I am updating some Schemas on the fly, but Schemas defined with s/defschema
don’t reflect these updates in the swagger UI. Is there some magic happening in ring-swagger where they refer back to the original var using the metadata maybe?
@borkdude Which routing lib is this?
I’m using yada.
Compojure-api stores the data on routing handler (which is a record).
Not sure about yada, but I think the Schemas aren't usually referred using vars but directly
yeah, the weird thing is when I remove the metadata explicitly, it works
but then I lose the name in the swagger UI
I made a hack which uses alter-var-root… but it’s kind of a mystery to me why this happens
Hmm, forget what I said. The problem is with just one of those named Schemas, not all of them.
One specific Schema that doesn’t reflect my changes when I assoc another key into it. When I turn s/defschema
into def
it does work…
it is accepted in a request though, just not displayed in the swagger UI example
Is there any way to "whitelist" a route so that the middleware defined at the top level is not applied?