GH-161 Check if WebJarHandler is already registered #166
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.
Resolves #161 by carefully checking if such a configured
SwaggerWebJarHandler
already exists and if not, registers one perSwaggerPlugin
. Includes a unit test to demonstrate and confirm the new behaviour.In the rare circumstance, that someone already would have a non
SwaggerWebJarHanlder
GET
handler on the configured swagger webjar route, this implementation would -in my opinion- rightfully fail.Replaces #162 due to polluted git history.