Change to ASP.NET Core Open API + Scalar#1345
Closed
jasontaylordev wants to merge 1 commit intomainfrom
Closed
Conversation
Owner
Author
|
Closing for now - will reopen when ready. |
|
Was actually just looking into this and digesting your comment:
The API documentation for ASP.NET Core Identity Api would not worry me that much. But I don't get the breaking changes to API only database migrations. How would replacing Swagger with Scalar affect this? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is WIP in progress. ASP.NET Core Identity API doesn't generate any documentation or organise operations.
There are potentially some breaking changes with regards to API only database migrations.