Deprecate Tingle.AspNetCore.Swagger and no longer publish it
#402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The extensions will be moved to a new package dependent on `Microsoft.AspNetCore.OpenApi` in a follow-up PR. The changes in Swashbuckle are becoming harder to keep up with. The new package has support for numerous scenarios, AoT, and inhertdoc XML comments. The code remains for reference purposes only.
mburumaxwell
force-pushed
the
deprecate-swashbuckle
branch
from
a3ec278 to
b63e115
Compare
mburumaxwell
added a commit
that referenced
this pull request
Feb 21, 2025
This adds support for `Microsoft.AspNetCore.OpenApi` which is meant to replace the `Swashbuckle.AspNetCore.Swagger*` packages. This started in #402 In this initial PR, trivial migrations have been done from `Tingle.AspNetCore.Swagger` to allow for early usage. Other code changes are expected to come later before a final release, such as XML comments for enum descriptions in case the framework does not end up adding them all.
mburumaxwell
added a commit
that referenced
this pull request
Feb 21, 2025
This adds support for `Microsoft.AspNetCore.OpenApi` which is meant to replace the `Swashbuckle.AspNetCore.Swagger*` packages. This started in #402 In this initial PR, trivial migrations have been done from `Tingle.AspNetCore.Swagger` to allow for early usage. Other code changes are expected to come later before a final release, such as XML comments for enum descriptions in case the framework does not end up adding them all.
mburumaxwell
added a commit
that referenced
this pull request
Feb 21, 2025
This adds support for `Microsoft.AspNetCore.OpenApi` which is meant to replace the `Swashbuckle.AspNetCore.Swagger*` packages. This started in #402 In this initial PR, trivial migrations have been done from `Tingle.AspNetCore.Swagger` to allow for early usage. Other code changes are expected to come later before a final release, such as XML comments for enum descriptions in case the framework does not end up adding them all.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The extensions will be moved to a new package dependent on
Microsoft.AspNetCore.OpenApiin a follow-up PR. The changes in Swashbuckle are becoming harder to keep up with. The new package has support for numerous scenarios, AoT, and inhertdoc XML comments as seen in dotnet/aspnetcore#39927 (comment)The code remains for reference purposes only.