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

support openapi 3.0 #46

Open
zhenhua32 opened this issue Mar 21, 2019 · 4 comments · May be fixed by #52
Open

support openapi 3.0 #46

zhenhua32 opened this issue Mar 21, 2019 · 4 comments · May be fixed by #52

Comments

@zhenhua32
Copy link

Is there any plan support openapi 3.0 ?

@maximdanilchenko
Copy link
Owner

Yes, I have such plans, and it is quite easy to implement (apispec has this feature). There will be an extra argument with openapi version.

playpauseandstop added a commit to playpauseandstop/aiohttp-apispec that referenced this issue May 12, 2019
Previously `AiohttpApiSpec` instantiate `ApiSpec` only for `openapi_version == '2.0'`,
this commit changes it by allowing pass `openapi_version` to `setup_aiohttp_apispec`
function and then use given value, while instantiating `ApiSpec` instance.

Fixes maximdanilchenko#46
@rugleb
Copy link

rugleb commented Feb 11, 2022

Any updates?

@ondrejkajinek
Copy link

#123 Similar PR, up to date with code, also provides correct schema for response body.

@arcan1s
Copy link

arcan1s commented Mar 28, 2023

according to apispec docs in: body parameter is not allowed for openapi 3.0. In fact, stoplight elements (https://elements-demo.stoplight.io/) doesn't render such parameters and is awaiting them in requestBody section

The issue persists with the latest git version

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

Successfully merging a pull request may close this issue.

5 participants