You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* 2.7: (47 commits)
Removed duplicate "long"s
terminate file with newline
move title back and move description to separate file as suggested in PR #4892
move title out of included file as suggested in PR #4892
Add possible values for widget_type
[#4842] Making 2 sentences
changes as suggested by WouterJ in pull request #4842
Add meaning of yellow icon for number of queries
Fixing bad link name
fix typo in event flow diagrams
Many fixes thanks to stof, WouterJ, xabbuh and dupuchba
added Jakub as a merger for the DomCrawler component
Changes thanks to WouterJ and xabbuh
[#5094] Removing mkdir - it's not needed (thanks xabbuh)
some tweaks to #4601
Moving index down to correct section
[#4989] Language tweaks and making the example simpler
Remove useless setLocale() call and add code block with locale setter
Finaly touches on translation locale setting note
Review note about setting the translator locale in a controller.
...
Copy file name to clipboardExpand all lines: components/asset/introduction.rst
+65-30Lines changed: 65 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,15 +26,16 @@ simple. Hardcoding URLs can be a disadvantage because:
26
26
asset. When using the Asset component, you can group assets in packages to
27
27
avoid repeating the common part of their path;
28
28
* **Versioning is difficult**: it has to be custom managed for each
29
-
application. Adding a version to the asset URLs is essential for some applications
30
-
because it allows to control how the assets are cached. The Asset component
31
-
allows to define different versioning strategies for each package;
29
+
application. Adding a version (e.g. ``main.css?v=5``) to the asset URLs
30
+
is essential for some applications because it allows you to control how
31
+
the assets are cached. The Asset component allows you to define different
32
+
versioning strategies for each package;
32
33
* **Moving assets location** is cumbersome and error-prone: it requires you to
33
34
carefully update the URLs of all assets included in all templates. The Asset
34
35
component allows to move assets effortlessly just by changing the base path
35
36
value associated with the package of assets;
36
-
* **It's nearly impossible to use multiple CDNs**: this technique requires to
37
-
change the URL of the asset randomly for each request. The Asset component
37
+
* **It's nearly impossible to use multiple CDNs**: this technique requires
38
+
you to change the URL of the asset randomly for each request. The Asset component
38
39
provides out-of-the-box support for any number of multiple CDNs, both regular
39
40
(``http://``) and secure (``https://``).
40
41
@@ -65,7 +66,7 @@ any versioning::
65
66
echo $package->getUrl('/image.png');
66
67
// result: /image.png
67
68
68
-
Packages implement the :class:`Symfony\\Component\\Asset\\PackageInterface`,
0 commit comments