Skip to content
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

Feature Request: Upgrade To Requiring Microsoft.OpenApi Version 1.6.0 #2606

Closed
EmperorArthur opened this issue Feb 7, 2023 · 1 comment · Fixed by #2795
Closed

Feature Request: Upgrade To Requiring Microsoft.OpenApi Version 1.6.0 #2606

EmperorArthur opened this issue Feb 7, 2023 · 1 comment · Fixed by #2795
Assignees

Comments

@EmperorArthur
Copy link

Feature Request

Please set the NuGet dependency to at least Microsoft.OpenApi Version 1.6.0.

Rationale

Until, NuGet/Home#5553 is resolved, bumping the minimum version is the only way to ensure all users have access to new features from dependencies. The only other way for users to gain access to new features is to install the transitive dependencies, negating all the benefits of PackageReference.

In this case, the largest change with the new version is Microsoft.OpenApi dropped support for .NET Framework.

Personal Reasons

I am making several calls to SwaggerGenOptions.SwaggerDoc(...), and found that most of Microsoft.OpenApi.Models.OpenApiInfo does not change. Unfortunately, the version Swashbuckle currently relies on (v.12.3) is over two years old, and does not have a copy constructor. The new version does. This meant I had to either install a transitive dependency, or re-implement library functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants