feat(pathbase): Add support for app.UsePathBase #2615
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 a minor change to add support for PathBase.
In cases where the API needs to use app.UsePathBase("some/path"), getting Swagger UI to conform to this path with RoutePrefix was a little involved. This change adds a PathBase property that should be set to the same value defined in app.UsePathBase().
From there, it checks the incoming request to see if path base is defined and the PathBase property is populated.
If PathBase is populated, but the incoming request path does not contain PathBase, then Swagger UI will not be displayed.
If PathBase is populated and the incoming request path contains the same PathBase value, then Swagger UI will be displayed.
If PathBase is not populated and the incoming request does not contain a PathBase value, then the normal workflow will display the Swagger UI.