First of all, thank for muuntaja and the nice ecosystem around HTTP.
I've been experimenting using reitit on top of aleph and, as a consequence, started using aleph also for http client. As aleph only tries to decode the body if the project contains cheshire and muuntaja is already part of the dependencies, I'd like to use it on top the http client to be able to parse the response body according to the content-type.
As I might use either json or transit+json, I think delegating the content type discovery and parsing to muuntaja would make more sense than having that on my end.
What do you think? Is that feasible (as in a desirable feature for muuntaja)?
Hi,
First of all, thank for muuntaja and the nice ecosystem around HTTP.
I've been experimenting using reitit on top of aleph and, as a consequence, started using aleph also for http client. As aleph only tries to decode the body if the project contains cheshire and muuntaja is already part of the dependencies, I'd like to use it on top the http client to be able to parse the response body according to the content-type.
As I might use either json or transit+json, I think delegating the content type discovery and parsing to muuntaja would make more sense than having that on my end.
What do you think? Is that feasible (as in a desirable feature for muuntaja)?