@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}})

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

Ok, that makes sense.

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

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

return that to clients?

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

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?