@@ -212,7 +212,7 @@ shifts the burden of fixing that deprecation to any contributor that
212
212
happens to submit a pull request shortly after a new vendor release is
213
213
made with that deprecation. To mitigate this, you can either use tighter
214
214
requirements, in the hope that dependencies will not introduce
215
- deprecations in a patch version, or even commit the Composer lock file,
215
+ deprecations in a patch version, or even commit the `` composer. lock`` file,
216
216
which would create another class of issues. Libraries will often use
217
217
``SYMFONY_DEPRECATIONS_HELPER=max[total]=999999 `` because of this. This
218
218
has the drawback of allowing contributions that introduce deprecations
@@ -227,7 +227,7 @@ be accounted for seperately, while deprecations triggered from a library
227
227
inside it will not (unless you reach 999999 of these), giving you
228
228
the best of both worlds.
229
229
230
- Direct and indirect deprecations
230
+ Direct and Indirect Deprecations
231
231
................................
232
232
233
233
When working on a project, you might be more interested in
@@ -258,7 +258,7 @@ Here is a summary that should help you pick the right configuration:
258
258
| | cannot afford to use one of the modes above. |
259
259
+------------------------+-----------------------------------------------------+
260
260
261
- Disabling the verbose output
261
+ Disabling the Verbose Output
262
262
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
263
263
264
264
By default, the bridge will display a detailed output with the number of
0 commit comments