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.
Currently JSON-Schemas are only generated for definitions in the
definitionsorcomponents/schemassection. 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.