Handling Non-JSON Responses with `yield* response.json`

I noticed that

yield* response.json;

yield* response.json;

on a request that does not return JSON results in a null value instead of an error. Is there a reason behind this choice? I'd expect it to throw an error so I can fallback with Effect.orElse

Communities Docs About Terms Privacy

Handling Non-JSON Responses with `yield* response.json` - Effect Community

Handling Non-JSON Responses with `yield* response.json`

Similar Threads

Handling Non-JSON Responses with `yield* response.json`

Similar Threads

Similar Threads

Similar Threads