-
Notifications
You must be signed in to change notification settings - Fork 58
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
OpenAPI 3.0 #63
Comments
Yes definitely - we're downstream of go-openapi parser, which handles spec parsing for us. And internally we're spec neutral (ish), so short answer: yes! |
Just waiting on go-openapi |
Thank you. Waiting patiently. I love DapperDox. :-) |
any update please ? |
Maybe depends on go-openapi/spec#21 ? |
That go-openapi issue is still open, and it looked like they were taking the discussion to their Slack channel. @zxchris are you aware of any progress? |
Same question here. If it helps move things along, I don't mind contributing some work. We really could use this for our own docs. |
Upstream is closed now. |
Would you support that in the near future?
https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md
Thx.
The text was updated successfully, but these errors were encountered: