-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 Spec 3.0.0 #312
Comments
@alairock yes this is on the road map. |
Any updates on this? Don't mean to rant but I just wasted an hour trying out my 3.0 yaml with this, while everything else works great, response examples arent rendered at all. Maybe you can add a Note to the readme pointing out that 3.0 isnt supported yet |
Hey @ThatBrianDude, I turned your idea into a pull request. Your time isn't wasted, if those 3.0 yaml files are public, could you send them to this fella? With API Flow properly supporting v3.0, nobody will need to manually upgrade v3.0 files. |
Any updates on this? |
@rugdealer I believe the plan is to port to ReactJS, then get stuck into the OpenAPI v3.0 efforts. I'm ready and waiting for this issue to be done, then I'll be happy to help with the OpenAPI v3.0 support. Open Source :) |
@philsturgeon OAS 3.0 support is coming together with #327. It's taking me a little longer time than I expected but I'm already close to the point I can publish this to a branch and let the community help me :) |
Closing this issue! |
Looks like that became available this last week. Is there an effort on-going to conform to the new specification?
The text was updated successfully, but these errors were encountered: