Marker interface for swagger ui index transformer #755
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.
close #745
as explained here it eases providing a custom SwaggerIndexTransformer by introducing an intermediary interface.
@bnasslahsen please note the 2nd commit. I factorized some behavior in the abstract class. The rationale is that if you have to duplicate this in mvc and reactive implementations then application creating a new transformation (for instance the linked example) will face the same issue and may have to rewrite same code.
If you're not comfortable with it I don't mind dropping this part; since you have
overwriteSwaggerDefaultUrl
andaddInitOauth
I supposed we can add other methods related to the default implementation.Since you rely on integration tests I did not add specific unit tests on the autoconfiguration but I can if you wish (I've done a few lately so it won't take long)