Is there a way to apply a content-type for all returned data, i.e., if I know that I'll always be returning JSON, to set that as applicable for every response? At the moment, I'm setting it within the response map that I return, i.e.,

{:status 200
     :headers JSON
     :body (utils/map->string results)}

where JSON is def'ed as (def ^:const JSON {"Content-Type": "application/json"})

you can put :produces #{"application/json"} on the top of your routes

scweet, trying...

That didn't quite work as expected

["/starships/:id" {:get get-starship-by-id
                       :produces #{"application/json"}
                       :parameters {:path {:id s/Int}}}]]

wrong place?

if you have Muuntaja middleware mounted, any response with a collection body and without Content-Type header is encoded into json/edn/transit, depending on what the client requested. It defaults to json (e.g. client is ok with anything)

e.g. {:status 200, :body {:this-is "Sparta!"}}

I don't think :produces does anything currently @vale?

Hi there a way to abort navigation for the front end stuff? on-navigate gets called after it’s happened?

@ikitommi thanks for the above tip, I can confirm that if the response body is a collection and if the muuntaja middleware is being used and if no content-type header is being set and if the client requests accept: application/json then yes, the response does come back as content-type: application/json

but...you can probably see where I'm going with this...

if the response is not a collection, but the rest (of the above) holds true

then the response has no content-type set and is served up "as-is"

I wouldd have thought, that if the accept had been set to application/json, the result would try to return (by default) content-type application/json

i.e., here's the request/response

wait

my sincere apologies, it still works - I forgot to re-eval my changes!

all is well 🙂