Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenAPI 3 field "requestBody" not interpreted #11

Open
ckrause opened this issue Nov 17, 2020 · 1 comment
Open

OpenAPI 3 field "requestBody" not interpreted #11

ckrause opened this issue Nov 17, 2020 · 1 comment

Comments

@ckrause
Copy link

ckrause commented Nov 17, 2020

bootprint-openapi is really great and I hope you find enough contributors to maintain it.

I noticed one issue: In OpenAPI 3, the request body parameter is defined using the requestBody field. This seems not to be interpreted by bootprint-openapi though. Can this be (easily) added?

The documentation of the request body field is here:
https://swagger.io/docs/specification/describing-request-body/

@nknapp
Copy link
Member

nknapp commented Nov 20, 2020

so far, OpenAPI 3 is not supported by bootprint-openapi. And at the moment, I am busy doing other things. I had started adding at least support for json-schema draft 7, but that code might still be in a branch in the old "bootprint-json-schema"-repo.

I hate to say this, but at the moment I cannot support this project and the transition to version 3.0 is a major amount of work.

I also think that the original purpose of having a printable documentation is leading into a false direction. I was thinking about making it more interactive a couple of years ago, but in our last project, we have used the original swagger-ui for that purpose and it worked pretty well, with a 3.0 spec....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants