Fork me on GitHub
#ring-swagger
<
2016-03-16
>
ikitommi09:03:53

@mikecarter: not directly, but you could do it yourself as a a) middleware b) custom meta-data handler

ikitommi09:03:39

(POST “/something” []
  :middleware [my-exists-mw-here]
  (ok …))

ikitommi09:03:04

with b it would be something like:

(POST “/something” []
  :exists? my-rule-here
  (ok …))

ikitommi09:03:33

Still looking forward to comments on the c-api Liberator support (https://github.com/metosin/compojure-api/issues/185). Could finalize it this week.

ikitommi09:03:22

Next up on the roadmap could be the buddy-integration for authentication & authorization.

mikecarter09:03:28

@ikitommi: thanks, will give it a go!

ikitommi12:03:55

haven't seen that. could you share the route definitions?

ikitommi12:03:27

is there a path with dynamic url? that might not work. e.g. (GET uri [] ...)

ikitommi12:03:16

are there a routes defined but not shown in the docs?

john.carnell12:03:21

All of the routes are defined and everything is functioning correctly. I just get an extra route, Let me throw the routes up here

ikitommi22:03:32

@john.carnell: clearly a bug -> the (GET “/“ [] …) at api root fails to resolve into a meaningful uri for the swagger-docs. Could you write an issue out of it so it gets fixed?

ikitommi22:03:40

but I guess you do not want to put the redirect into the swagger-docs, so you could wrap that route into undocumented - > (undocumented (GET “/“ [] …))

ikitommi22:03:25

also, the example uses the pre 1.0.0 swagger-ui & docs format, they do work, but require extra import. There is a “better” way to do it with 1.0.0, see https://github.com/metosin/compojure-api/wiki/Swagger-integration

ikitommi22:03:33

hope this helps.