Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Templating] Adding AssetMapper to asset() function #21132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 6.4
Choose a base branch
from

Conversation

ThomasLandauer
Copy link
Contributor

Page: https://symfony.com/doc/6.4/templates.html#linking-to-css-javascript-and-image-assets

There is another link to AssetMapper just one screen further down - maybe you want to merge them somehow: https://symfony.com/doc/6.4/templates.html#build-versioning-more-advanced-css-javascript-and-image-handling

My point here is that the main advantage of the asset() function IMO is not the subdirectory scenario, but rather: If you later switch to AssetMapper, it saves you a lot of time if you've already used asset() everywhere.

Page: https://symfony.com/doc/6.4/templates.html#linking-to-css-javascript-and-image-assets

There is another link to AssetMapper just one screen further down - maybe you want to merge them somehow: https://symfony.com/doc/6.4/templates.html#build-versioning-more-advanced-css-javascript-and-image-handling

My point here is that the main advantage of the `asset()` function IMO is not the subdirectory scenario, but rather: If you *later* switch to AssetMapper, it saves you a lot of time if you've already used `asset()` everywhere.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants