[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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Open

ThomasLandauer wants to merge1 commit intosymfony:6.4

base:6.4

Choose a base branch

fromThomasLandauer:patch-12

Open

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

ThomasLandauer wants to merge1 commit intosymfony:6.4fromThomasLandauer:patch-12

Conversation

Copy link

Contributor

ThomasLandauer commentedJun 24, 2025

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 theasset() function IMO is not the subdirectory scenario, but rather: If youlater switch to AssetMapper, it saves you a lot of time if you've already usedasset() everywhere.

[Templating] Adding AssetMapper toasset() function

117be68

Page:https://symfony.com/doc/6.4/templates.html#linking-to-css-javascript-and-image-assetsThere 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-handlingMy 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.