-
Notifications
You must be signed in to change notification settings - Fork 506
OpenAPI 3.0.x Support #518
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
Comments
OpenAPI v3 also gives a warning when there are |
Any roadmap for this issue ? |
I understand this project is undergoing changes in how it operates, but is there any update on this? I potentially would be willing to help with this, as the OpenAPI 3.0.0 spec provides features I would like to use |
I think this is a good time to add support for version 3. What do you think? (@SteadBytes , @ziirish, @a-luna, @j5awry ) |
I think that we would need another project like : flask-restplus3 that will implement Swagger 3.0 and because of name it could also drop support for python2 which should be officialy dropped support anyway next year in January, |
Just want to chime in to support this thread. I just want to simply add JWT as a security scheme, which is not defined in Swagge2.0 but in OpenAPI3.0. |
Any update on this? The world is moving on, lets move on with flask-restplus as well! GO FLASK-RESTPLUS!! |
Any update on this? |
Hi @sptremblay , I am all for OpenApi 3.0! However currently the project is having some difficulties regarding ownership 😕 Please take a look at the discussion here #743 (comment) . I will be hopefully be updating it with my decision tomorrow 👍 |
I'm somewhat new to swagger, but if I understand it correctly, flask_restplus currently outputs the swagger.json in the old "Swagger 2.0" format. Are there any plans to also support the OpenAPI 3.0.x specification?
Background: We are having some trouble with the way swagger handles authorizations in the cookie, that have apparently been fixed in OpenAPI 3.0.0 (according to this issue on the openapi repo)
The text was updated successfully, but these errors were encountered: