You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently JSON-Schemas are only generated for definitions in the definitions or components/schemas section. This is alright if your full request and response bodies are defined there, but that is not always the case in every OpenAPI spec. It would be nice if paths/<path>/<httpmethod>/requestBody/content/<mimetype>/schema> and paths/<path>/<httpmethod>/responses/<httpcode>/content/<mimetype>/schema> could also be traversed.
The generated filenames will probably be long and ugly, but that is something I can live with.
The text was updated successfully, but these errors were encountered:
zeusttu
added a commit
to zeusttu/openapi2jsonschema
that referenced
this issue
May 3, 2019
Include schemas from:
paths/<path>/<httpmethod>/requestBody/content/<mimetype>/schema
paths/<path>/<httpmethod>/responses/<httpcode>/content/<mimetype>/schema
Closesinstrumenta#25
Do not downcase filenames
Closesinstrumenta#20
Move new functionality to separate function
Make "content" key in body definition optional
This was committed as a GitHub review suggestion.
Commit message suggested by Github:
Update openapi2jsonschema/util.py
Co-authored-by: Adam Kitain <[email protected]>
Currently JSON-Schemas are only generated for definitions in the
definitions
orcomponents/schemas
section. This is alright if your full request and response bodies are defined there, but that is not always the case in every OpenAPI spec. It would be nice ifpaths/<path>/<httpmethod>/requestBody/content/<mimetype>/schema>
andpaths/<path>/<httpmethod>/responses/<httpcode>/content/<mimetype>/schema>
could also be traversed.The generated filenames will probably be long and ugly, but that is something I can live with.
The text was updated successfully, but these errors were encountered: