Skip to content

Commit 6c19fa7

Browse files
Changing versionadded 5.1 to note
Reasons: * Info about 5.1 doesn't make sense in 5.4 anymore. * Link to `configureContainer` was dead anyway.
1 parent 881ebd8 commit 6c19fa7

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

configuration.rst

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -60,13 +60,11 @@ configure your applications. Symfony lets you choose between YAML, XML and PHP
6060
and throughout the Symfony documentation, all configuration examples will be
6161
shown in these three formats.
6262

63-
.. versionadded:: 5.1
63+
.. note::
6464

65-
Starting from Symfony 5.1, by default Symfony only loads the configuration
65+
By default, Symfony only loads the configuration
6666
files defined in YAML format. If you define configuration in XML and/or PHP
67-
formats, update the ``src/Kernel.php`` file to add support for the ``.xml``
68-
and ``.php`` file extensions by overriding the
69-
:method:`Symfony\\Component\\HttpKernel\\Kernel::configureContainer` method::
67+
formats, update the ``src/Kernel.php`` file::
7068

7169
// src/Kernel.php
7270
use Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator;
@@ -93,8 +91,8 @@ shown in these three formats.
9391
}
9492

9593
There isn't any practical difference between formats. In fact, Symfony
96-
transforms and caches all of them into PHP before running the application, so
97-
there's not even any performance difference between them.
94+
transforms all of them into PHP and caches them before running the application, so
95+
there's not even any performance difference.
9896

9997
YAML is used by default when installing packages because it's concise and very
10098
readable. These are the main advantages and disadvantages of each format:

0 commit comments

Comments
 (0)