@@ -75,7 +75,6 @@ Configuration
75
75
* `packages `_
76
76
* `version `_
77
77
* `version_format `_
78
- * `version_strategy `_
79
78
* `templating `_
80
79
* `hinclude_default_template `_
81
80
* :ref: `form <reference-templating-form >`
@@ -946,8 +945,6 @@ collection each time it generates an asset's path:
946
945
),
947
946
));
948
947
949
- .. _reference-framework-assets-packages :
950
-
951
948
packages
952
949
........
953
950
@@ -1016,7 +1013,6 @@ Each package can configure the following options:
1016
1013
* :ref: `base_urls <reference-assets-base-urls >`
1017
1014
* :ref: `version <reference-framework-assets-version >`
1018
1015
* :ref: `version_format <reference-assets-version-format >`
1019
- * :ref: `version_strategy <reference-framework-assets-version_strategy >`
1020
1016
1021
1017
.. _reference-framework-assets-version :
1022
1018
.. _ref-framework-assets-version :
@@ -1094,7 +1090,6 @@ option.
1094
1090
``version ``. This makes it easier to increment the cache on each
1095
1091
deployment.
1096
1092
1097
- .. _reference-framework-assets-version-format :
1098
1093
.. _reference-templating-version-format :
1099
1094
.. _reference-assets-version-format :
1100
1095
@@ -1135,16 +1130,6 @@ is set to ``5``, the asset's path would be ``/images/logo.png?version=5``.
1135
1130
any URL rewriting. The latter option is useful if you would like older
1136
1131
asset versions to remain accessible at their original URL.
1137
1132
1138
- .. _reference-framework-assets-version_strategy :
1139
-
1140
- version_strategy
1141
- ................
1142
-
1143
- **type **: ``string `` **default **: null
1144
-
1145
- The service id of the :doc: `asset version strategy </frontend/custom_version_strategy >`
1146
- applied to the assets.
1147
-
1148
1133
templating
1149
1134
~~~~~~~~~~
1150
1135
0 commit comments