This repository was archived by the owner on Jan 21, 2026. It is now read-only.
Merged
Conversation
bradygaster
approved these changes
Sep 10, 2020
Member
bradygaster
left a comment
bradygaster
left a comment
There was a problem hiding this comment.
Excellent and cc @coolcsh fyi
This was referenced Sep 11, 2020
Merged
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
As of .NET 5 RC1, the
dotnet new webapitemplate now has a default start url ofswagger. Because the default Swashbuckle-generated OpenAPI description doesn't contain a Servers element, this will put HttpRepl users that launch from VS/VS Code into a pit of failure by having a base address ofhttps://localhost:{port}/swagger/, even though the API is, by default, based at the root. The user won't be able to navigate their API at all, because you can't navigate "above" the base address.Since it is unlikely a user would put their API inside the
/swaggerpath, we will special-case this scenario and remove that from the url. We will give the user an escape hatch via the preference if they do put their API under that path.