Trailing whitespaces

carusogabriel · carusogabriel · commit fc9e35158989 · 2017-12-31T00:50:40.000-02:00
diff --git a/bundles/installation.rst b/bundles/installation.rst
@@ -48,7 +48,7 @@ version, include it as the second argument of the `composer require`_ command:
 B) Enable the Bundle
 --------------------
 
-At this point, the bundle is installed in your Symfony project (e.g. 
+At this point, the bundle is installed in your Symfony project (e.g.
 ``vendor/friendsofsymfony/``) and the autoloader recognizes its classes.
 The only thing you need to do now is register the bundle in ``AppKernel``::
 
diff --git a/changelog.rst b/changelog.rst
@@ -1,6 +1,6 @@
 .. index::
     single: CHANGELOG
-    
+
 .. !! CAUTION !!
    This file is automatically generated. Do not add new changelog
    items when preparing a pull request.
diff --git a/components/console/helpers/questionhelper.rst b/components/console/helpers/questionhelper.rst
@@ -174,7 +174,7 @@ will be autocompleted as the user types::
     {
         // ...
         $helper = $this->getHelper('question');
-        
+
         $bundles = array('AcmeDemoBundle', 'AcmeBlogBundle', 'AcmeStoreBundle');
         $question = new Question('Please enter the name of a bundle', 'FooBundle');
         $question->setAutocompleterValues($bundles);
@@ -195,7 +195,7 @@ convenient for passwords::
     {
         // ...
         $helper = $this->getHelper('question');
-        
+
         $question = new Question('What is the database password?');
         $question->setHidden(true);
         $question->setHiddenFallback(false);
@@ -230,7 +230,7 @@ method::
     {
         // ...
         $helper = $this->getHelper('question');
-        
+
         $question = new Question('Please enter the name of the bundle', 'AppBundle');
         $question->setNormalizer(function ($value) {
             // $value can be null here
diff --git a/components/dom_crawler.rst b/components/dom_crawler.rst
@@ -339,13 +339,13 @@ a :class:`Symfony\\Component\\DomCrawler\\Form` object that represents the
 form that the button lives in::
 
     // button example: <button id="my-super-button" type="submit">My super button</button>
-    
+
     // you can get button by its label
     $form = $crawler->selectButton('My super button')->form();
-    
+
     // or by button id (#my-super-button) if the button doesn't have a label
     $form = $crawler->selectButton('my-super-button')->form();
-    
+
     // or you can filter the whole form, for example a form has a class attribute: <form class="form-vertical" method="POST">
     $crawler->filter('.form-vertical')->form();
 
diff --git a/components/expression_language/extending.rst b/components/expression_language/extending.rst
@@ -64,7 +64,7 @@ to add custom functions. To do so, you can create a new expression provider by
 creating a class that implements
 :class:`Symfony\\Component\\ExpressionLanguage\\ExpressionFunctionProviderInterface`.
 
-This interface requires one method: 
+This interface requires one method:
 :method:`Symfony\\Component\\ExpressionLanguage\\ExpressionFunctionProviderInterface::getFunctions`,
 which returns an array of expression functions (instances of
 :class:`Symfony\\Component\\ExpressionLanguage\\ExpressionFunction`) to
diff --git a/components/index.rst b/components/index.rst
@@ -4,6 +4,6 @@ The Components
 .. toctree::
     :maxdepth: 1
     :glob:
-    
+
     using_components
     *
diff --git a/components/security/authentication.rst b/components/security/authentication.rst
@@ -15,7 +15,7 @@ firewall map is able to extract the user's credentials from the current
 a token, containing these credentials. The next thing the listener should
 do is ask the authentication manager to validate the given token, and return
 an *authenticated* token if the supplied credentials were found to be valid.
-The listener should then store the authenticated token using 
+The listener should then store the authenticated token using
 :class:`the token storage <Symfony\\Component\\Security\\Core\\Authentication\\Token\\Storage\\TokenStorageInterface>`::
 
     use Symfony\Component\Security\Http\Firewall\ListenerInterface;
diff --git a/components/stopwatch.rst b/components/stopwatch.rst
@@ -34,10 +34,10 @@ microtime by yourself. Instead, use the simple
     $event = $stopwatch->stop('eventName');
 
 The :class:`Symfony\\Component\\Stopwatch\\StopwatchEvent` object can be retrieved
-from the  :method:`Symfony\\Component\\Stopwatch\\Stopwatch::start`, 
-:method:`Symfony\\Component\\Stopwatch\\Stopwatch::stop`, 
-:method:`Symfony\\Component\\Stopwatch\\Stopwatch::lap` and 
-:method:`Symfony\\Component\\Stopwatch\\Stopwatch::getEvent` methods. 
+from the  :method:`Symfony\\Component\\Stopwatch\\Stopwatch::start`,
+:method:`Symfony\\Component\\Stopwatch\\Stopwatch::stop`,
+:method:`Symfony\\Component\\Stopwatch\\Stopwatch::lap` and
+:method:`Symfony\\Component\\Stopwatch\\Stopwatch::getEvent` methods.
 The latter should be used when you need to retrieve the duration of an event
 while it is still running.
 
diff --git a/components/validator/metadata.rst b/components/validator/metadata.rst
@@ -1,72 +1,72 @@
-.. index::
-    single: Validator; Metadata
-
-Metadata
-========
-
-The :class:`Symfony\\Component\\Validator\\Mapping\\ClassMetadata` class
-represents and manages all the configured constraints on a given class.
-
-Properties
-----------
-
-The Validator component can validate public, protected or private properties.
-The following example shows how to validate that the ``$firstName`` property of
-the ``Author`` class has at least 3 characters::
-
-    // ...
-    use Symfony\Component\Validator\Mapping\ClassMetadata;
-    use Symfony\Component\Validator\Constraints as Assert;
-
-    class Author
-    {
-        private $firstName;
-
-        public static function loadValidatorMetadata(ClassMetadata $metadata)
-        {
-            $metadata->addPropertyConstraint('firstName', new Assert\NotBlank());
-            $metadata->addPropertyConstraint(
-                'firstName',
-                new Assert\Length(array("min" => 3))
-            );
-        }
-    }
-
-Getters
--------
-
-Constraints can also be applied to the value returned by any public *getter*
-method, which are the methods whose names start with ``get``, ``has`` or ``is``.
-This feature allows to validate your objects dynamically.
-
-Suppose that, for security reasons, you want to validate that a password field
-doesn't match the first name of the user. First, create a public method called
-``isPasswordSafe()`` to define this custom validation logic::
-
-    public function isPasswordSafe()
-    {
-        return $this->firstName !== $this->password;
-    }
-
-Then, add the Validator component configuration to the class::
-
-    // ...
-    use Symfony\Component\Validator\Mapping\ClassMetadata;
-    use Symfony\Component\Validator\Constraints as Assert;
-
-    class Author
-    {
-        public static function loadValidatorMetadata(ClassMetadata $metadata)
-        {
-            $metadata->addGetterConstraint('passwordSafe', new Assert\IsTrue(array(
-                'message' => 'The password cannot match your first name',
-            )));
-        }
-    }
-
-Classes
--------
-
-Some constraints allow to validate the entire object. For example, the
-:doc:`Callback </reference/constraints/Callback>` constraint is a generic
-constraint that's applied to the class itself.
+.. index::
+    single: Validator; Metadata
+
+Metadata
+========
+
+The :class:`Symfony\\Component\\Validator\\Mapping\\ClassMetadata` class
+represents and manages all the configured constraints on a given class.
+
+Properties
+----------
+
+The Validator component can validate public, protected or private properties.
+The following example shows how to validate that the ``$firstName`` property of
+the ``Author`` class has at least 3 characters::
+
+    // ...
+    use Symfony\Component\Validator\Mapping\ClassMetadata;
+    use Symfony\Component\Validator\Constraints as Assert;
+
+    class Author
+    {
+        private $firstName;
+
+        public static function loadValidatorMetadata(ClassMetadata $metadata)
+        {
+            $metadata->addPropertyConstraint('firstName', new Assert\NotBlank());
+            $metadata->addPropertyConstraint(
+                'firstName',
+                new Assert\Length(array("min" => 3))
+            );
+        }
+    }
+
+Getters
+-------
+
+Constraints can also be applied to the value returned by any public *getter*
+method, which are the methods whose names start with ``get``, ``has`` or ``is``.
+This feature allows to validate your objects dynamically.
+
+Suppose that, for security reasons, you want to validate that a password field
+doesn't match the first name of the user. First, create a public method called
+``isPasswordSafe()`` to define this custom validation logic::
+
+    public function isPasswordSafe()
+    {
+        return $this->firstName !== $this->password;
+    }
+
+Then, add the Validator component configuration to the class::
+
+    // ...
+    use Symfony\Component\Validator\Mapping\ClassMetadata;
+    use Symfony\Component\Validator\Constraints as Assert;
+
+    class Author
+    {
+        public static function loadValidatorMetadata(ClassMetadata $metadata)
+        {
+            $metadata->addGetterConstraint('passwordSafe', new Assert\IsTrue(array(
+                'message' => 'The password cannot match your first name',
+            )));
+        }
+    }
+
+Classes
+-------
+
+Some constraints allow to validate the entire object. For example, the
+:doc:`Callback </reference/constraints/Callback>` constraint is a generic
+constraint that's applied to the class itself.
diff --git a/components/validator/resources.rst b/components/validator/resources.rst
@@ -179,13 +179,13 @@ Using a Custom MetadataFactory
 ------------------------------
 
 All the loaders and the cache are passed to an instance of
-:class:`Symfony\\Component\\Validator\\Mapping\\Factory\\LazyLoadingMetadataFactory`. 
+:class:`Symfony\\Component\\Validator\\Mapping\\Factory\\LazyLoadingMetadataFactory`.
 This class is responsible for creating a ``ClassMetadata`` instance from all the
 configured resources.
 
 You can also use a custom metadata factory implementation by creating a class
 which implements
-:class:`Symfony\\Component\\Validator\\Mapping\\Factory\\MetadataFactoryInterface`. 
+:class:`Symfony\\Component\\Validator\\Mapping\\Factory\\MetadataFactoryInterface`.
 You can set this custom implementation using
 :method:`Symfony\\Component\\Validator\\ValidatorBuilder::setMetadataFactory`::
 
diff --git a/console/command_in_controller.rst b/console/command_in_controller.rst
@@ -55,7 +55,7 @@ Run this command from inside your controller via::
 
             // return the output, don't use if you used NullOutput()
             $content = $output->fetch();
-            
+
             // return new Response(""), if you used NullOutput()
             return new Response($content);
         }
diff --git a/contributing/code/bugs.rst b/contributing/code/bugs.rst
@@ -26,8 +26,8 @@ If your problem definitely looks like a bug, report it using the official bug
 * Describe the steps needed to reproduce the bug with short code examples
   (providing a unit test that illustrates the bug is best);
 
-* If the bug you experienced is not obvious or affects more than one layer, 
-  providing a simple failing unit test may not be sufficient. In this case, 
+* If the bug you experienced is not obvious or affects more than one layer,
+  providing a simple failing unit test may not be sufficient. In this case,
   please :doc:`provide a reproducer </contributing/code/reproducer>`;
 
 * Give as much detail as possible about your environment (OS, PHP version,
diff --git a/create_framework/front_controller.rst b/create_framework/front_controller.rst
@@ -140,7 +140,7 @@ web root directory:
 
     example.com
     ├── composer.json
-    ├── composer.lock    
+    ├── composer.lock
     ├── src
     │   └── pages
     │       ├── hello.php
diff --git a/create_framework/http_kernel_httpkernel_class.rst b/create_framework/http_kernel_httpkernel_class.rst
@@ -64,7 +64,7 @@ attributes with route parameters.
 Our code is now much more concise and surprisingly more robust and more
 powerful than ever. For instance, use the built-in ``ExceptionListener`` to
 make your error management configurable::
-    
+
     $errorHandler = function (Symfony\Component\Debug\Exception\FlattenException $exception) {
         $msg = 'Something went wrong! ('.$exception->getMessage().')';
 
diff --git a/create_framework/separation_of_concerns.rst b/create_framework/separation_of_concerns.rst
@@ -142,7 +142,7 @@ To sum up, here is the new file layout:
 
     example.com
     ├── composer.json
-    ├── composer.lock    
+    ├── composer.lock
     ├── src
     │   ├── app.php
     │   └── Simplex
diff --git a/deployment/platformsh.rst b/deployment/platformsh.rst
@@ -36,7 +36,7 @@ Platform.sh how to deploy your application (read more about
 
     # The name of this app. Must be unique within a project.
     name: myphpproject
-    
+
     # The type of the application to build.
     type: php:5.6
     build:
diff --git a/form/action_method.rst b/form/action_method.rst
@@ -88,7 +88,7 @@ options:
                 // ...
             }
         }
-    
+
 
     .. code-block:: php-standalone
 
diff --git a/form/form_collections.rst b/form/form_collections.rst
@@ -293,7 +293,7 @@ add the ``allow_add`` option to your collection field::
     public function buildForm(FormBuilderInterface $builder, array $options)
     {
         $builder->add('description');
-        
+
         $builder->add('tags', 'collection', array(
             'type'         => new TagType(),
             'options'      => array('label' => false),
@@ -408,7 +408,7 @@ one example:
         // Replace '__name__label__' in the prototype's HTML to
         // instead be a number based on how many items we have
         // newForm = newForm.replace(/__name__label__/g, index);
-        
+
         // Replace '__name__' in the prototype's HTML to
         // instead be a number based on how many items we have
         newForm = newForm.replace(/__name__/g, index);
diff --git a/form/without_class.rst b/form/without_class.rst
@@ -101,7 +101,7 @@ but here's a short example:
     If you are using validation groups, you need to either reference the
     ``Default`` group when creating the form, or set the correct group on
     the constraint you are adding.
-    
+
     .. code-block:: php
 
         new NotBlank(array('groups' => array('create', 'update')));
diff --git a/http_cache.rst b/http_cache.rst
@@ -149,7 +149,7 @@ information about cache hits and misses.
     website or when you deploy your website to a shared host where you cannot
     install anything beyond PHP code. But being written in PHP, it cannot
     be as fast as a proxy written in C.
-    
+
     Fortunately, since all reverse proxies are effectively the same, you should
     be able to switch to something more robust - like Varnish - without any problems.
     See :doc:`How to use Varnish </http_cache/varnish>`
@@ -191,7 +191,7 @@ These four headers are used to help cache your responses via *two* different mod
 
     All of the HTTP headers you'll read about are *not* invented by Symfony! They're
     part of an HTTP specification that's used by sites all over the web. To dig deeper
-    into HTTP Caching, check out the documents `RFC 7234 - Caching`_ and 
+    into HTTP Caching, check out the documents `RFC 7234 - Caching`_ and
     `RFC 7232 - Conditional Requests`_.
 
     As a web developer, you are strongly urged to read the specification. Its
diff --git a/logging.rst b/logging.rst
@@ -15,7 +15,7 @@ your controller::
         $logger = $this->get('logger');
         $logger->info('I just got the logger');
         $logger->error('An error occurred');
-        
+
         $logger->critical('I left the oven on!', array(
             // include extra "context" info in your logs
             'cause' => 'in_hurry',
diff --git a/reference/configuration/doctrine.rst b/reference/configuration/doctrine.rst
diff --git a/reference/configuration/twig.rst b/reference/configuration/twig.rst
diff --git a/reference/forms/types/number.rst b/reference/forms/types/number.rst
diff --git a/routing/extra_information.rst b/routing/extra_information.rst
diff --git a/security/firewall_restriction.rst b/security/firewall_restriction.rst
diff --git a/security/host_restriction.rst b/security/host_restriction.rst
diff --git a/security/target_path.rst b/security/target_path.rst
diff --git a/setup/file_permissions.rst b/setup/file_permissions.rst
diff --git a/validation/sequence_provider.rst b/validation/sequence_provider.rst

Original file line number	Diff line number	Diff line change
`@@ -4,6 +4,6 @@ The Components`
`4`	`4`	`.. toctree::`
`5`	`5`	`:maxdepth: 1`
`6`	`6`	`:glob:`
`7`		`-`
	`7`	`+`
`8`	`8`	`using_components`
`9`	`9`	`*`