can anyone give advice on how i might use pjson over cheshire for json parsing in a compojure-api app?

noticing our app is spending a lot of time in json parsing

@jstokes: Might be possible by disabling built-in json support (`[:format :formats]`) and adding your own middleware

But setting :formats option will also affect swagger docs

Maybe you can just use your own middleware without any settings, ring-middleware-format is probably no-op if the request body has already been parsed

and custom middleware is applied before ring-middleware-format?

Compojure-api just embeds ring-middleware-format with some specific options

@jstokes: Yes. If you do something like (pre 1.0 example): (defapi app' ...) (def app (-> app' wrap-own-mw))

own-mw will be applied before calling api handler

got it

ill give it a shot, thanks @juhoteperi

I have a question around ring-middleware-format

I need to have json rq/rs with properties names in camelCaseFormat but would like to work in my system with maps with :kebab-style-keys

Hmm, I think r-m-f should allow options to cheshire

I tried to use {:format {:params-opts {:json {:key-fn ->kebab-case-keyword}}}

but then the problem is that my schema says for example user-id (this is actually my internal format) while the json format should be userId

Hmm the default json format might be :json-kw instead of :json

Oh right

let me check :json-kw

I don't think there is a solution for having correct docs in this case currently

@juhoteperi: :json-kw worked - thanks

but discrepancy between schema and actual json format is still there

any ideas if it can be fixed easily?

Not sure how it could be fixed as different formats could have different names. It would require support from JSON Schema/Swagger

One possibility would be to force same key format for all formats

I see, I guess I have to stick to camelCase keys in my code for now 😕