Skip to content

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

Open
mmanhertz opened this issue Aug 31, 2018 · 9 comments
Open

OpenAPI 3.0.x Support #518

mmanhertz opened this issue Aug 31, 2018 · 9 comments

Comments

@mmanhertz
Copy link

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)

@ErikBjare
Copy link

OpenAPI v3 also gives a warning when there are $schema keys in the output spec (as is no longer valid). See this issue for how it was discovered: ActivityWatch/activitywatch#252

@sptremblay
Copy link

Any roadmap for this issue ?

@RPiAwesomeness
Copy link

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

@xarpy
Copy link

xarpy commented Aug 21, 2019

I think this is a good time to add support for version 3. What do you think? (@SteadBytes , @ziirish, @a-luna, @j5awry )

@tincumagic
Copy link

tincumagic commented Aug 21, 2019

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,
The reason is that Swagger 3.0 format has a enough differences ... in formatting that keeping parallel support for both would mean a lot of additional difficulties, additional conditioning if swagger2 or swagger3. Plus we would need to keep the JavaScript for both which will bloat more the library. Plus if you use Swagger3 you normally don't want to move back to Swagger2.

@jbkoh
Copy link

jbkoh commented Oct 25, 2019

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.

@ishtiaque-khan
Copy link

Any update on this? The world is moving on, lets move on with flask-restplus as well!

GO FLASK-RESTPLUS!!

@ghost
Copy link

ghost commented Dec 13, 2019

Any update on this?

@SteadBytes
Copy link
Collaborator

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 👍

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

9 participants