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

OpenAPI 3.0 #63

Open
SWSAmor opened this issue Jul 20, 2017 · 8 comments
Open

OpenAPI 3.0 #63

SWSAmor opened this issue Jul 20, 2017 · 8 comments

Comments

@SWSAmor
Copy link

SWSAmor commented Jul 20, 2017

Would you support that in the near future?
https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md

Thx.

@zxchris
Copy link
Collaborator

zxchris commented Aug 4, 2017

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!

@zxchris
Copy link
Collaborator

zxchris commented Aug 4, 2017

Just waiting on go-openapi

@SWSAmor
Copy link
Author

SWSAmor commented Aug 4, 2017

Thank you. Waiting patiently. I love DapperDox. :-)

@alexjomin
Copy link

any update please ?

@hotgazpacho
Copy link

Maybe depends on go-openapi/spec#21 ?

@polarweasel
Copy link

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?

@david-l-riley
Copy link

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.

@quazgar
Copy link

quazgar commented Jun 30, 2021

Upstream is closed now.

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

7 participants