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

Open API V3 Support #26

Open
ndamclean opened this issue Jan 30, 2020 · 7 comments
Open

Open API V3 Support #26

ndamclean opened this issue Jan 30, 2020 · 7 comments
Labels
enhancement New feature or request

Comments

@ndamclean
Copy link

flask_restplus currently outputs the swagger.json in the old "Swagger 2.0" format. Are there any plans to also support the OpenAPI 3.x specification?

OpenAPI 3.x has better support for different authentication methods, including JWT token-based authentication.

@SVilgelm SVilgelm added the enhancement New feature or request label Feb 12, 2020
@twsl
Copy link

twsl commented Feb 17, 2020

This includes updating the 2 year old swagger-ui-dist

@Cheaterman
Copy link

Any updates on this? :-) I don't mind Swagger 2.0 myself, but I'm getting requests for OpenAPI 3.x. I'd be happy to help if needed!

@sherghan
Copy link

Could you at least write something about plans for OpenAPI 3 in the readme.md?
Currently it does not even recognize the existence of the new major version of the format.

With no such information one could easily get a false impression that it is implemented, working fine and there is not much to talk about.

...It's not that 3.0 appeared yesterday.

@francesco086
Copy link

I think this is a rather serious issue. This is what refrains me from using this library...

@rawouter
Copy link

I'm being requested to move to OpenAPI 3 for a rather big project, do you have any roadmap?

@j5awry
Copy link
Contributor

j5awry commented Apr 14, 2021

I want to bring up some big points here --

  1. the logic for creating the Swagger docs are ingrained in the RestX classes. So it's a heavy lift with the current architecture to support both 2.0 and 3.0.
  2. We've had discussions of moving the modeling from the RestX specific classes to a more generalized framework: Flask-RESTX Models Re-Design #59

I completely understand the need to move to OpenAPI 3.0, but it's going to be a large lift. We welcome contributions from all over, and I'm working through some more of the backlog of open PRs and issues.

@mauvilsa
Copy link

Just out of curiosity. Is there a python library that is able to convert swagger 2.0 to openapi 3.0? If there is such library, would it make sense that flask-restx have the option to use this to switch between 2.0 and 3.0? Maybe just do this as a short term solution until the more generalized framework is done.

I know some time ago I used some converter from swagger 2.0 to openapi 3.0. A few details were not converted correctly so I stopped doing that. But don't know if it is impossible to do this conversion perfectly or was the converter that had some bug or missing features. Anyway, just throwing out an idea in case it could be useful.

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

No branches or pull requests

9 participants