Feature Request: OpenAPI 3 support

[c4milo]

https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md

[achew22]

@c4milo, Can you elaborate on what it is you're interested in that isn't available today?

[c4milo]

@achew22, feature wise, nothing. What's concerning to me right now is that https://github.com/swagger-api/swagger-js/tree/2.x is no longer active. Most development effort is going towards supporting OpenAPI v3.

[zxy198717]

+1

[johanbrandhorst]

The OpenAPI 3.0 spec has added support for Authentication (JWT, Oath, HTTP Basic), which is something that is missing from 2.0. I think this would make it worthwhile to migrate to generating 3.0 compliant definitions.

[jsw]

Also oneof?

[tamalsaha]

I suppose https://github.com/go-openapi/spec3 will be needed first.

[ivucica]

@johanbrandhorst Strictly speaking, that's not something that makes v3 support a must and a requirement. Consider that OpenAPI v2 does support OAuth2 authentication, Basic authentication and API keys.

I don't see in that PR where OpenAPI v3 adds JWT, and I suppose you meant OAuth2 and not OATH (different thigns)?

What I see as a new thing in that PR you quoted is "HTTP Bearer" and "Multiple Flows", which both may be useful. (Even though Bearer will be usually used with OAuth2, anyway, there might be people out there not using it that way.)

@tamalsaha That would be the right way to go, but protoc-gen-swagger has OpenAPI v2 schema, so that's not a blocker either.

[veqryn]

OpenAPI v3.0.0 adds support for specifying multiple servers (hosts).

[unship]

oneof sematics is a pain point for us

[jones77]

OpenAPI 3.0 adds support for nullable types, 2.0 doesn't support them: swagger-api/swagger-editor#1364 (comment)

[johanbrandhorst]

I'm pretty sure there's an extension for V2 (x-nullable?).

[johanbrandhorst]

#900 is a real issue that would be covered by this.