-
Notifications
You must be signed in to change notification settings - Fork 73
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
Is there a way to generate openapi v3? #76
Comments
hi, I am not aware of other projects that can generate a v3 document with data available in go-restful. With contributors , we can start creating a v3 branch in this project and modify the code such it is conform the v3 spec. |
ok, thank you! |
@SVilgelm I can think of a couple of reasons to introduce v3 branch instead:
|
I did some research and seems only this https://github.com/getkin/kin-openapi/tree/master/openapi3 project is alive, so v3 branch will require to use kin lib instead of swagger I'm not sure how good the https://github.com/getkin/kin-openapi/tree/master/openapi2, but maybe it worth to use it instead of swagger as well for v2? |
forget about my last suggestion about using kin for v2, it will break existent code for all users for sure |
so kin for v3 is still a reasonable choice? |
it is up to you, but seems it supports v3 pretty well. I have created my own lib for v3.1, but it depends on go v1.18, because of generics: https://github.com/sv-tools/openapi |
I'm confusing... |
it is not supported yet, I used kin-openapi to convert v2 to v3, worked well, with some hacks of course. It really depends what you want from the v3 API. If you need just some basic features, that are supported by v2, then kin library will work for you, but if you need something like |
I see that this projects heavily uses Swagger v2, but is there a way to generate v3? Maybe you can recommend a project that we can use instead of go-restful-openapi but which works with go-restful?
The text was updated successfully, but these errors were encountered: