Swashbuckle.webapi: OpenAPI 3.0 Support
Is there any plan to support generating OpenAPI 3.0 definitions?
furier
All 13 comments
Sure, should not be a problem, as long as more people sign up as maintainers, see Issue #1053
heldersepu
on 29 May 2017
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? :)
furier
on 29 May 2017
+1
ghost
on 21 Dec 2017
@ptomkiel-oktawave
If you want to "+1" an Issue on github, click on the "Pick reaction" button:
heldersepu
on 21 Dec 2017
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.
darrelmiller
on 22 May 2018
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!
sivan-r
on 11 Dec 2018
No plans to backport here I鈥檓 afraid
domaindrivendev
on 11 Dec 2018
Thank you for the quick reply.
Any idea how to upgrade an existing project to openApi 3 without upgrading to .Net core?
sivan-r
on 12 Dec 2018
You could try NSwag - it鈥檚 an alternative library that generates Swagger, among other things. I believe it supports OpenAPI 3.0.
domaindrivendev
on 12 Dec 2018
Any update for this?
jerrychoubear
on 23 Jan 2019
NSwag does not support OpenAPI 3 yet: https://github.com/RSuter/NSwag/issues/945
giggio
on 5 Feb 2019
@giggio NSwag does support OAS3 but not every feature yet...
RicoSuter
on 19 Mar 2019
Would be awesome to see OpenAPi 3.0 backported to .Net
mcox-ng
on 16 May 2020
Related issues
djem3000
路
5Comments
maheshmohandas
路
4Comments
josephearl
路
4Comments
raaga123
路
4Comments
whippet-rider
路
5Comments
Most helpful comment
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.