Upgrade to Symfony 6.4 & Asset Mapper #2
Merged
Conversation
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
ogizanagi
force-pushed
the
sf-64-asset-mapper
branch
2 times, most recently
from
9ac967c to
8de6053
Compare
ogizanagi
force-pushed
the
sf-64-asset-mapper
branch
2 times, most recently
from
71b840f to
7795fc3
Compare
ogizanagi
force-pushed
the
sf-64-asset-mapper
branch
from
7795fc3 to
9c302ae
Compare
ogizanagi
changed the title
ogizanagi
changed the title
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.
To experiment with asset mapper & stenope, according to StenopePHP/Stenope#173 issue.
Also, this will be the future of assets handling with Symfony, no more bundler implied : symfony/demo#1449 (comment)