OpenAPI 3.0 Support

[furier]

Is there any plan to support generating OpenAPI 3.0 definitions?

[heldersepu]

Sure, should not be a problem, as long as more people sign up as maintainers, see Issue #1053

[furier]

Doesnt the equestion also apply to Swashbuckle.AspNetCore ? Or did you mean that you need more maintainers overall to up support for OpenAPI 3.0 and not just Swagger 2.0 for both projects? :)

[ghost]

+1

[heldersepu]

@ptomkiel-oktawave
If you want to "+1" an Issue on github, click on the "Pick reaction" button:

[darrelmiller]

I'm working on it for ASP NET core Swashbuckle. Once that is done, if there is sufficient demand, I'd be prepared to backport it here.

[sivan-r]

Hi,
I noticed that the beta version for ASP NET core Swashbuckle has been released.
Any news about if and when it will be back-ported here?
Thanks!

[domaindrivendev]

No plans to backport here I’m afraid

[sivan-r]

Thank you for the quick reply.
Any idea how to upgrade an existing project to openApi 3 without upgrading to .Net core?

[domaindrivendev]

You could try NSwag - it’s an alternative library that generates Swagger, among other things. I believe it supports OpenAPI 3.0.

[jerrychoubear]

Any update for this?

[giggio]

NSwag does not support OpenAPI 3 yet: RicoSuter/NSwag#945

[RicoSuter]

@giggio NSwag does support OAS3 but not every feature yet...

[mcox-ng]

Would be awesome to see OpenAPi 3.0 backported to .Net

[foscjos2]

I know this is an old ticket but I'd like to chime in that getting OAPI 3.0 support would be very nice. Not sure how tough it would be to implement it here.

[bugproof]

This repo is not active. See https://github.com/domaindrivendev/Swashbuckle.AspNetCore
It has OAPI 3.0 generator.

[sourabhagrawal23]

@bugproof The OAPI 3.0 generator is for dot Net core, right? Is there any way to get OAPI 3.0 without upgrading from .Net to .NetCore