Proposal swag 2.0 using open api 3.0

[Nerzal]

Hey everyone.
As the support of Swagger 2.0 is pretty stable now, we should start to make a list of all features / changes we need to support Open Api 3.0.

We might create a new 2.0 milestone and move/create Open Api 3.0 support issues in there.

[superdave]

I would love this, we've been holding off on it at work because it's not OpenAPI 3. What's best for me to help?

[ubogdan]

@superdave PR is always welcome.

[tylfin]

Would love this to get access to the oneOf functionality for schema responses

[alandtsang]

Does it support OpenAPI Specification 3 now?

[Nerzal]

nope.
The spec lib which is used under the hood does only support Swagger 2.0.

We'd need to switch to a spec lib that supports OpenAPI 3, if there is such a lib by now

[ipfans]

@Nerzal maybe just try https://github.com/getkin/kin-openapi

[OneCricketeer]

I've found a way to generate openapi3 specs from the output of this project

#386 (comment)

[hotrungnhan]

upppppppppppppppppppppppppppppppppppppp!

[vtopc]

Any progress with this? Except for workaround

[ubogdan]

I don't think It will happen any time soon.

[Nerzal]

i have a branch, where i refactore swaggo to use open api 3.0 specs, but will still take some weeks/months until it is finished, as i do not have that much time at hand to complete it

[ubogdan]

We can't support this kind of change overnight.
More than that, this will introduce breaking changes, and this has to go with v2.
On the other hand, we see many requests regarding improvements and bug fixes for the current parser.
Working on a new version too early will introduce the additional overhead of merging the v1 fixes in the new branch.