minor #11508 fix indention (OskarStark)

This PR was merged into the 3.4 branch.

Discussion
----------

fix indention

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/roadmap for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `master` for features of unreleased versions).

-->

Commits
-------

cbe6e45 fix indention

Author: javiereguiluz

bundles/extension.rst

@@ -141,7 +141,7 @@ I/O operations and increases the application performance.
 
 .. versionadded:: 3.2
 
-   The ``addAnnotatedClassesToCompile()`` method was introduced in Symfony 3.2.
+    The ``addAnnotatedClassesToCompile()`` method was introduced in Symfony 3.2.
 
 Your bundles can also add their own classes into this file thanks to the
 ``addClassesToCompile()`` and ``addAnnotatedClassesToCompile()`` methods (both
@@ -178,7 +178,7 @@ class names::
 
 .. versionadded:: 3.2
 
-   The option to add classes to compile using patterns was introduced in Symfony 3.2.
+    The option to add classes to compile using patterns was introduced in Symfony 3.2.
 
 The classes to compile can also be added using file path patterns::
 

components/cache.rst

@@ -33,8 +33,8 @@ Cache (PSR-6) Versus Simple Cache (PSR-16)
 This component includes *two* different approaches to caching:
 
 :ref:`PSR-6 Caching <cache-component-psr6-caching>`:
-     A fully-featured cache system, which includes cache "pools", more advanced
-     cache "items", and :ref:`cache tagging for invalidation <cache-component-tags>`.
+    A fully-featured cache system, which includes cache "pools", more advanced
+    cache "items", and :ref:`cache tagging for invalidation <cache-component-tags>`.
 
 :ref:`PSR-16 Simple Caching <cache-component-psr16-caching>`:
     A simple way to store, fetch and remove items from a cache.

components/console/single_command_tool.rst

@@ -19,15 +19,15 @@ it is possible to remove this need by declaring a single command application::
     use Symfony\Component\Console\Output\OutputInterface;
 
     (new Application('echo', '1.0.0'))
-      ->register('echo')
-          ->addArgument('foo', InputArgument::OPTIONAL, 'The directory')
-          ->addOption('bar', null, InputOption::VALUE_REQUIRED)
-          ->setCode(function(InputInterface $input, OutputInterface $output) {
-              // output arguments and options
-          })
-      ->getApplication()
-      ->setDefaultCommand('echo', true) // Single command application
-      ->run();
+        ->register('echo')
+            ->addArgument('foo', InputArgument::OPTIONAL, 'The directory')
+            ->addOption('bar', null, InputOption::VALUE_REQUIRED)
+            ->setCode(function(InputInterface $input, OutputInterface $output) {
+                // output arguments and options
+            })
+        ->getApplication()
+        ->setDefaultCommand('echo', true) // Single command application
+        ->run();
 
 The method :method:`Symfony\\Component\\Console\\Application::setDefaultCommand`
 accepts a boolean as second parameter. If true, the command ``echo`` will then

components/phpunit_bridge.rst

@@ -48,7 +48,7 @@ to register a new `test listener`_ called ``SymfonyTestsListener``:
 
     <!-- http://phpunit.de/manual/6.0/en/appendixes.configuration.html -->
     <phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-             xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/6.0/phpunit.xsd"
+        xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/6.0/phpunit.xsd"
     >
 
         <!-- ... -->
@@ -172,7 +172,7 @@ message, enclosed with ``/``. For example, with:
 
     <!-- http://phpunit.de/manual/6.0/en/appendixes.configuration.html -->
     <phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-             xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/6.0/phpunit.xsd"
+        xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/6.0/phpunit.xsd"
     >
 
         <!-- ... -->
@@ -501,7 +501,7 @@ namespaces in the ``phpunit.xml`` file, as done for example in the
 
     <!-- http://phpunit.de/manual/4.1/en/appendixes.configuration.html -->
     <phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-             xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/4.1/phpunit.xsd"
+        xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/4.1/phpunit.xsd"
     >
 
         <!-- ... -->
@@ -645,7 +645,7 @@ Add the following configuration to the ``phpunit.xml.dist`` file:
 
     <!-- http://phpunit.de/manual/6.0/en/appendixes.configuration.html -->
     <phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-             xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/6.0/phpunit.xsd"
+        xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/6.0/phpunit.xsd"
     >
 
         <!-- ... -->

components/translation/usage.rst

@@ -452,7 +452,7 @@ loaded/dumped when using this component inside a Symfony application:
 
     <?xml version="1.0" encoding="UTF-8"?>
     <xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0"
-           srcLang="fr-FR" trgLang="en-US">
+        srcLang="fr-FR" trgLang="en-US">
         <file id="messages.en_US">
             <unit id="LCa0a2j">
                 <notes>

components/var_dumper/advanced.rst

@@ -59,15 +59,15 @@ you can configure these limits:
     items. Specifying ``-1`` removes the limit.
 
 :method:`Symfony\\Component\\VarDumper\\Cloner\\VarCloner::setMinDepth`
-    .. versionadded:: 3.4
-
-        The ``setMinDepth()`` method was introduced in Symfony 3.4.
-
     Configures the minimum tree depth where we are guaranteed to clone
     all the items. After this depth is reached, only ``setMaxItems``
     items will be cloned. The default value is ``1``, which is consistent
     with older Symfony versions.
 
+    .. versionadded:: 3.4
+
+        The ``setMinDepth()`` method was introduced in Symfony 3.4.
+
 :method:`Symfony\\Component\\VarDumper\\Cloner\\VarCloner::setMaxString`
     Configures the maximum number of characters that will be cloned before
     cutting overlong strings.  Specifying ``-1`` removes the limit.
@@ -85,12 +85,12 @@ Before dumping it, you can further limit the resulting
     Removes internal objects' handles for sparser output (useful for tests).
 
 :method:`Symfony\\Component\\VarDumper\\Cloner\\Data::seek`
+    Selects only subparts of already cloned arrays, objects or resources.
+
     .. versionadded:: 3.2
 
         The ``seek()`` method was introduced in Symfony 3.2.
 
-    Selects only subparts of already cloned arrays, objects or resources.
-
 Unlike the previous limits on cloners that remove data on purpose, these can
 be changed back and forth before dumping since they do not affect the
 intermediate representation internally.

components/web_link.rst

@@ -5,8 +5,8 @@
 The WebLink Component
 ======================
 
-   The WebLink component provides tools to manage the ``Link`` HTTP header needed
-   for `Web Linking`_ when using `HTTP/2 Server Push`_ as well as `Resource Hints`_.
+    The WebLink component provides tools to manage the ``Link`` HTTP header needed
+    for `Web Linking`_ when using `HTTP/2 Server Push`_ as well as `Resource Hints`_.
 
 Installation
 ------------

console/input.rst

@@ -166,8 +166,8 @@ flag:
 
 .. tip::
 
-     You can also declare a one-letter shortcut that you can call with a single
-     dash, like ``-i``::
+    You can also declare a one-letter shortcut that you can call with a single
+    dash, like ``-i``::
 
         $this
             // ...

contributing/documentation/index.rst

@@ -5,21 +5,21 @@ These short articles explain everything you need to contribute to the Symfony
 documentation:
 
 :doc:`The Contribution Process </contributing/documentation/overview>`
-  Explains the steps to follow to contribute fixes and new contents. It's the
-  same contribution process followed by most open source projects, so you may
-  already know everything that is needed.
+    Explains the steps to follow to contribute fixes and new contents. It's the
+    same contribution process followed by most open source projects, so you may
+    already know everything that is needed.
 
 :doc:`Documentation Formats </contributing/documentation/format>`
-  Explains the technical details of the reStructuredText format that is used to
-  write the docs. Skip it if you are already familiar with this format.
+    Explains the technical details of the reStructuredText format that is used to
+    write the docs. Skip it if you are already familiar with this format.
 
 :doc:`Documentation Standards </contributing/documentation/standards>`
-  Explains how to write docs and code examples to match the style and tone of
-  the rest of the existing documentation.
+    Explains how to write docs and code examples to match the style and tone of
+    the rest of the existing documentation.
 
 :doc:`License </contributing/documentation/license>`
-  Explains the details of the Creative Commons BY-SA 3.0 license used for the
-  Symfony Documentation.
+    Explains the details of the Creative Commons BY-SA 3.0 license used for the
+    Symfony Documentation.
 
 .. toctree::
     :hidden:

create_framework/routing.rst

@@ -93,23 +93,23 @@ The ``match()`` method takes a request path and returns an array of attributes
 (notice that the matched route is automatically stored under the special
 ``_route`` attribute)::
 
-    print_r($matcher->match('/bye'));
-    /* Gives:
+    $matcher->match('/bye');
+    /* Result:
     [
         '_route' => 'bye',
     ];
     */
 
-    print_r($matcher->match('/hello/Fabien'));
-    /* Gives:
+    $matcher->match('/hello/Fabien');
+    /* Result:
     [
         'name' => 'Fabien',
         '_route' => 'hello',
     ];
     */
 
-    print_r($matcher->match('/hello'));
-    /* Gives:
+    $matcher->match('/hello');
+    /* Result:
     [
         'name' => 'World',
         '_route' => 'hello',

deployment/azure-website.rst

@@ -404,32 +404,32 @@ application, configure it with the following content:
 .. code-block:: xml
 
     <configuration>
-      <system.webServer>
-        <rewrite>
-          <rules>
-            <clear/>
-            <rule name="BlockAccessToPublic" patternSyntax="Wildcard" stopProcessing="true">
-              <match url="*"/>
-              <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
-                <add input="{URL}" pattern="/web/*"/>
-              </conditions>
-              <action type="CustomResponse" statusCode="403" statusReason="Forbidden: Access is denied." statusDescription="You do not have permission to view this directory or page using the credentials that you supplied."/>
-            </rule>
-            <rule name="RewriteAssetsToPublic" stopProcessing="true">
-              <match url="^(.*)(\.css|\.js|\.jpg|\.png|\.gif|\.ico)$"/>
-              <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
-              </conditions>
-              <action type="Rewrite" url="web/{R:0}"/>
-            </rule>
-            <rule name="RewriteRequestsToPublic" stopProcessing="true">
-              <match url="^(.*)$"/>
-              <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
-              </conditions>
-              <action type="Rewrite" url="web/app.php/{R:0}"/>
-            </rule>
-          </rules>
-        </rewrite>
-      </system.webServer>
+        <system.webServer>
+            <rewrite>
+                <rules>
+                    <clear/>
+                    <rule name="BlockAccessToPublic" patternSyntax="Wildcard" stopProcessing="true">
+                        <match url="*"/>
+                        <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
+                            <add input="{URL}" pattern="/web/*"/>
+                        </conditions>
+                        <action type="CustomResponse" statusCode="403" statusReason="Forbidden: Access is denied." statusDescription="You do not have permission to view this directory or page using the credentials that you supplied."/>
+                    </rule>
+                    <rule name="RewriteAssetsToPublic" stopProcessing="true">
+                        <match url="^(.*)(\.css|\.js|\.jpg|\.png|\.gif|\.ico)$"/>
+                        <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
+                        </conditions>
+                        <action type="Rewrite" url="web/{R:0}"/>
+                    </rule>
+                    <rule name="RewriteRequestsToPublic" stopProcessing="true">
+                        <match url="^(.*)$"/>
+                        <conditions logicalGrouping="MatchAll" trackAllCaptures="false">
+                        </conditions>
+                        <action type="Rewrite" url="web/app.php/{R:0}"/>
+                    </rule>
+                </rules>
+            </rewrite>
+        </system.webServer>
     </configuration>
 
 As you can see, the latest rule ``RewriteRequestsToPublic`` is responsible for

deployment/fortrabbit.rst

@@ -270,8 +270,8 @@ Commit and push
 
 .. note::
 
-   The first ``git push`` takes much longer as all composer dependencies get
-   downloaded. All subsequent deploys are done within seconds.
+    The first ``git push`` takes much longer as all composer dependencies get
+    downloaded. All subsequent deploys are done within seconds.
 
 That's it! Your application is being deployed on fortrabbit. More information
 about `database migrations and tunneling`_ can be found in the fortrabbit

deployment/platformsh.rst

@@ -40,7 +40,7 @@ Platform.sh how to deploy your application (read more about
     # The type of the application to build.
     type: php:5.6
     build:
-      flavor: composer
+        flavor: composer
 
     # The relationships of the application with services or other applications.
     # The left-hand side is the name of the relationship as it will be exposed
@@ -68,10 +68,10 @@ Platform.sh how to deploy your application (read more about
     # The hooks that will be performed when the package is deployed.
     hooks:
         build: |
-          rm web/app_dev.php
-          php bin/console --env=prod assetic:dump --no-debug
+            rm web/app_dev.php
+            php bin/console --env=prod assetic:dump --no-debug
         deploy: |
-          php bin/console --env=prod cache:clear
+            php bin/console --env=prod cache:clear
 
 For best practices, you should also add a ``.platform`` folder at the root of
 your Git repository which contains the following files:
@@ -111,7 +111,7 @@ following file (it's your role to add this file to your code base)::
 
     foreach ($relationships['database'] as $endpoint) {
         if (empty($endpoint['query']['is_master'])) {
-          continue;
+            continue;
         }
 
         $container->setParameter('database_driver', 'pdo_' . $endpoint['scheme']);

doctrine/reverse_engineering.rst

@@ -74,15 +74,18 @@ The generated ``BlogPost.orm.xml`` metadata file looks as follows:
 .. code-block:: xml
 
     <?xml version="1.0" encoding="UTF-8"?>
-    <doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping https://doctrine-project.org/schemas/orm/doctrine-mapping.xsd">
-      <entity name="AppBundle\Entity\BlogPost" table="blog_post">
-        <id name="id" type="bigint" column="id">
-          <generator strategy="IDENTITY"/>
-        </id>
-        <field name="title" type="string" column="title" length="100" nullable="false"/>
-        <field name="content" type="text" column="content" nullable="false"/>
-        <field name="createdAt" type="datetime" column="created_at" nullable="false"/>
-      </entity>
+    <doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping"
+        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+        xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping
+            https://doctrine-project.org/schemas/orm/doctrine-mapping.xsd">
+        <entity name="AppBundle\Entity\BlogPost" table="blog_post">
+            <id name="id" type="bigint" column="id">
+                <generator strategy="IDENTITY"/>
+            </id>
+            <field name="title" type="string" column="title" length="100" nullable="false"/>
+            <field name="content" type="text" column="content" nullable="false"/>
+            <field name="createdAt" type="datetime" column="created_at" nullable="false"/>
+        </entity>
     </doctrine-mapping>
 
 Once the metadata files are generated, you can ask Doctrine to build related

forms.rst

@@ -557,8 +557,8 @@ the correct values of a number of field options.
 
 .. caution::
 
-  These field options are *only* guessed if you're using Symfony to guess
-  the field type (i.e. omit or pass ``null`` as the second argument to ``add()``).
+    These field options are *only* guessed if you're using Symfony to guess
+    the field type (i.e. omit or pass ``null`` as the second argument to ``add()``).
 
 If you'd like to change one of the guessed values, you can override it by
 passing the option in the options field array::

frontend/assetic/php.rst

@@ -108,10 +108,10 @@ First, configure a new ``scssphp`` Assetic filter:
         // app/config/config.php
         $container->loadFromExtension('assetic', [
             'filters' => [
-                 'scssphp' => [
-                     'formatter' => 'Leafo\ScssPhp\Formatter\Compressed',
-                 ],
-                 // ...
+                'scssphp' => [
+                    'formatter' => 'Leafo\ScssPhp\Formatter\Compressed',
+                ],
+                // ...
             ],
         ]);
 
@@ -181,8 +181,8 @@ First, configure a new ``jsqueeze`` Assetic filter as follows:
         // app/config/config.php
         $container->loadFromExtension('assetic', [
             'filters' => [
-                 'jsqueeze' => null,
-                 // ...
+                'jsqueeze' => null,
+                // ...
             ],
         ]);
 

reference/configuration/debug.rst

@@ -79,7 +79,7 @@ destination for dumps. Typically, you would set this to ``php://stderr``:
 
         # app/config/config.yml
         debug:
-           dump_destination: php://stderr
+            dump_destination: php://stderr
 
     .. code-block:: xml
 
@@ -99,5 +99,5 @@ destination for dumps. Typically, you would set this to ``php://stderr``:
 
         // app/config/config.php
         $container->loadFromExtension('debug', [
-           'dump_destination' => 'php://stderr',
+            'dump_destination' => 'php://stderr',
         ]);