it seems that if i have a s/either in a schema describing the input of a route in c-api, swagger-ui shows only one of the branches. validation works for both alternatives. am i doing something wrong or is it the way it works?

also, schemas that have non-kw keys don't show up in swagger-ui

@shem: swagger spec doesn't support either. See my 2y old issue on it: https://github.com/OAI/OpenAPI-Specification/issues/57. README of ring-swagger lists how the schemas are mapped json schema. So, you are doing it right.

non-kw keys, could you paste an example?

{s/Int {:name s/Str :type s/Str}

ah, that could be represented with Swagger. Open and issue to ring-swagger?

patterned propertied in JSON Schema I think.

ok, will do. thanks for clarification!

np