Add MapSwaggerUI for endpoint routing #2472
Open
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.
fixes #2061
fixes #1726
alternative to #2266
Has the exact same behavior with regard to options as the
UseSwaggerUI
overload with setupAction. That is it loads anySwaggerUIOptions
provided via DI and applies the same defaults as saidUseSwaggerUI
overload.Comparing it to
MapSwagger
the main difference is the avoidance of yet another options type. Which is, as far as I can tell a straight copy of the original one. What was the rationale behind that design?