ring-swagger & compojure-api
ikitommi 2018-03-20T05:52:40.000139Z

@jmckitrick The endpoint-macros produce code for the endpoint and the order of things defined might matter. You can call

(macroexpand-1 `(GET "/auth" [] :query-params [x :- Long] {:status 200, :body {:x x}})
to see what get’s generated.

ikitommi 2018-03-20T05:53:29.000196Z

there is a buddy-auth example in https://github.com/yogthos/memory-hole

jmckitrick 2018-03-20T15:19:00.000113Z

Ok, that makes sense.

jmckitrick 2018-03-20T15:19:27.001028Z

How difficult would it be to use expound messages for spec failures during validation and coercion?

ikitommi 2018-03-20T15:35:51.000314Z

Shoudn't be hard, as it only interprets the :problems. But... It returns one mega-string.

ikitommi 2018-03-20T15:36:08.000334Z

return that to clients?

ikitommi 2018-03-20T15:36:58.000095Z

or let clients use expound as the :problems go over the wire already. Well, mostly. Can't serialize function refs

jmckitrick 2018-03-20T18:19:46.000315Z

I have a question about documentation. For the Authentication and Authorization section, what should go there, besides what would apply to base compojure? What points should be covered?