swagger1st
swagger1st copied to clipboard
A Clojure Ring handler that parses, validates and routes requests based on your Swagger definitions
Hi, Thanks for amazing project! Are there any plans on upgrading swagger-ui to the recent versions to 3.x.x? (https://www.npmjs.com/package/swagger-ui#compatibility)
Resolves #80 I added an additional check to account for when the body of a request isn't just an array object, but rather an object with an array parameter. Like...
With schema parameters like: ``` parameters: - in: "body" name: "body" description: "JSON array of words to add to the corpus" required: true schema: type: "object" required: - words properties:...
Currently the s1st parser serializes json responses with automatically: https://github.com/zalando/swagger1st/blob/183cba7e30e62da6a23df9078e7062830885d72e/src/io/sarnowski/swagger1st/parser.clj#L344 Unfortunately this happens only if the content type matches "application/json" exactly. In other words * "application/problem+json" * "application/json; charset=UTF-8" *...
parameters with 'in: body' parameter only works under the Operation Object. Check 'Fixed Fields' of 'Path Item Object' on (http://swagger.io/specification/)
It seems that path parameters (ones that have property "in: path") are passed to handler function as is. This causes a problem since handler should now process values these parameters...
Currently `api/throw-error` yields the following json: ``` json { "message": "Error", "details": {...} } ``` It would be cool if this could be changed to the [application/problem+json](https://tools.ietf.org/html/draft-nottingham-http-problem-06) RFC. The function...
As we expected swagger1st to allow undefined properties in definitions, but it didn't, it took me a while to find out actually we can allow this using an option(:allow-undefined-keys) in...
The New Relic dependency is out of scope of the project and is not required in most cases. OTOH it can be useful as a separate Ring middleware somewhere else....