An easy way to avoid throwing on non-200 statuses about req HOT 6 CLOSED

If you don’t want to define an instance of MonadHttp you can always use runReq and pass HttpConfig there directly. In the config you’ll need to set httpConfigCheckResponse to something like \_ _ _ -> Nothing.

from req.

Does this answer your question? Can we close this one?

from req.

Ah, I see. Thank you very much for helping @mrkkrp, good to close!

from req.

This is also shown in the docs and readme 😉

from req.

@mrkkrp right, just checked Haddock and found mentions of httpConfigCheckResponse. However, in README I couldn't find anything except

Just define handleHttpException accordingly when making your monad instance of MonadHttp and it will play together seamlessly.

Maybe it's worth adding a small note or example? TBH, I was pretty surprised to receive an exception on non-200 response, not exactly the default of a least surprise.

Anyway, sorry for the silly question. I'm new to Haskell and its ecosystem and failed to figure out from the first try how http-client and req play together ¯\_(ツ)_/¯

from req.

Ah, sorry I just was thinking about runReq itself vs defining a new instance. Never mind.

from req.