Configurable asset package#3764
Merged
Merged
Conversation
Fix unit tests cs fix minor fixes
e53deff to
8c69482
Compare
Contributor
Author
|
The cs-fixer test seems to be invalid, the diff does not contain the failing change anymore. |
soyuka
approved these changes
Nov 8, 2020
Member
|
thanks @smatyas ! |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR introduces a new config parameter:
asset_packageIt enables the users to specify a custom asset package (as in Symfony framework) to be used by the Swagger UI template.
In this way, we have more fine-grained control over the asset url generations.
The new parameter is optional with a
nulldefault value. It results in the sameasset(...)twig function calls as it was before.Example usage of the new parameter:
and the corresponding symfony framework setup example: