Merge branch '2.8' into 3.3

* 2.8:
  Some fixes for testing/* articles in 2.7 docs
  Fixed some issues in PHPUnit XML config examples
  Removed a wrong note about controllers as services
  Removed lots of redundant contents
  [symfony#8650] Minor rewording
  [symfony#8649] Small reword
  Improved the link to the Symfony events reference
  Minor fixes for upload_file.rst
  Fixed a typo
  Added getSubscribedEvents() to UserLocaleSubscriber
  Reworded the explanation about service tags
  Reworded the intro of reference/dic_tags.rst
  Fixed RST syntax issue
  Revamped the reference/events.rst article
  Change some docs to be gender-neutral

controller/upload_file.rst

@@ -108,7 +108,7 @@ to :doc:`customize form rendering </form/form_customization>`):
 Finally, you need to update the code of the controller that handles the form::
 
     // src/AppBundle/Controller/ProductController.php
-    namespace AppBundle\ProductController;
+    namespace AppBundle\Controller;
 
     use Sensio\Bundle\FrameworkExtraBundle\Configuration\Route;
     use Symfony\Bundle\FrameworkBundle\Controller\Controller;

event_dispatcher.rst

@@ -64,8 +64,8 @@ The most common way to listen to an event is to register an **event listener**::
 
     Each event receives a slightly different type of ``$event`` object. For
     the ``kernel.exception`` event, it is :class:`Symfony\\Component\\HttpKernel\\Event\\GetResponseForExceptionEvent`.
-    To see what type of object each event listener receives, see :class:`Symfony\\Component\\HttpKernel\\KernelEvents`
-    or the documentation about the specific event you're listening to.
+    Check out the :doc:`Symfony events reference </reference/events>` to see
+    what type of object each event provides.
 
 Now that the class is created, you just need to register it as a service and
 notify Symfony that it is a "listener" on the ``kernel.exception`` event by

form/events.rst

@@ -282,7 +282,7 @@ Creating and binding an event listener to the form is very easy::
                 return;
             }
 
-            // Check whether the user has chosen to display his email or not.
+            // Check whether the user has chosen to display their email or not.
             // If the data was submitted previously, the additional value that is
             // included in the request variables needs to be removed.
             if (true === $user['show_email']) {
@@ -363,7 +363,7 @@ Event subscribers have different uses:
             $form = $event->getForm();
 
             // Check whether the user from the initial data has chosen to
-            // display his email or not.
+            // display their email or not.
             if (true === $user->isShowEmail()) {
                 $form->add('email', EmailType::class);
             }
@@ -378,7 +378,7 @@ Event subscribers have different uses:
                 return;
             }
 
-            // Check whether the user has chosen to display his email or not.
+            // Check whether the user has chosen to display their email or not.
             // If the data was submitted previously, the additional value that
             // is included in the request variables needs to be removed.
             if (true === $user['show_email']) {

reference/dic_tags.rst

@@ -1,16 +1,12 @@
-The Dependency Injection Tags
+Built-in Symfony Service Tags
 =============================
 
-Dependency Injection Tags are little strings that can be applied to a service
-to "flag" it to be used in some special way. For example, if you have a
-service that you would like to register as a listener to one of Symfony's
-core events, you can flag it with the ``kernel.event_listener`` tag.
+:doc:`Service tags </service_container/tags>` are the mechanism used by the
+:doc:`DependencyInjection component </components/dependency_injection>` to flag
+services that require special processing, like console commands or Twig extensions.
 
-You can learn a little bit more about "tags" by reading the ":doc:`/service_container/tags`"
-article.
-
-Below is information about all of the tags available inside Symfony. There
-may also be tags in other bundles you use that aren't listed here.
+These are the most common tags provided by Symfony components, but in your
+application there could be more tags available provided by third-party bundles:
 
 ========================================  ========================================================================
 Tag Name                                  Usage

reference/events.rst

@@ -1,17 +1,17 @@
-Symfony Framework Events
-========================
+Built-in Symfony Events
+=======================
 
-When the Symfony Framework (or anything using the :class:`Symfony\\Component\\HttpKernel\\HttpKernel`)
-handles a request, a few core events are dispatched so that you can add
-listeners throughout the process. These are called the "kernel events".
-For a larger explanation, see :doc:`/components/http_kernel`.
+During the handling of an HTTP request, the Symfony framework (or any
+application using the :doc:`HttpKernel component </components/http_kernel>`)
+dispatches some :doc:`events </event_dispatcher>` which you can use to modify
+how the request is handled.
 
 Kernel Events
 -------------
 
-Each event dispatched by the kernel is a subclass of
-:class:`Symfony\\Component\\HttpKernel\\Event\\KernelEvent`. This means
-that each event has access to the following information:
+Each event dispatched by the HttpKernel component is a subclass of
+:class:`Symfony\\Component\\HttpKernel\\Event\\KernelEvent`, which provides the
+following information:
 
 :method:`Symfony\\Component\\HttpKernel\\Event\\KernelEvent::getRequestType`
     Returns the *type* of the request (``HttpKernelInterface::MASTER_REQUEST``
@@ -31,67 +31,60 @@ that each event has access to the following information:
 **Event Class**: :class:`Symfony\\Component\\HttpKernel\\Event\\GetResponseEvent`
 
 This event is dispatched very early in Symfony, before the controller is
-determined.
+determined. It's useful to add information to the Request or return a Response
+early to stop the handling of the request.
 
 .. seealso::
 
     Read more on the :ref:`kernel.request event <component-http-kernel-kernel-request>`.
 
-These are the built-in Symfony listeners registered to this event:
+Execute this command to find out which listeners are registered for this event and
+their priorities:
 
-=============================================================================  ========
-Listener Class Name                                                            Priority
-=============================================================================  ========
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\ProfilerListener`       1024
-:class:`Symfony\\Bundle\\FrameworkBundle\\EventListener\\TestSessionListener`  192
-:class:`Symfony\\Bundle\\FrameworkBundle\\EventListener\\SessionListener`      128
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\RouterListener`         32
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\LocaleListener`         16
-:class:`Symfony\\Component\\Security\\Http\\Firewall`                          8
-=============================================================================  ========
+.. code-block:: terminal
+
+    $ php bin/console debug:event-dispatcher kernel.request
 
 ``kernel.controller``
 ~~~~~~~~~~~~~~~~~~~~~
 
 **Event Class**: :class:`Symfony\\Component\\HttpKernel\\Event\\FilterControllerEvent`
 
-This event can be an entry point used to modify the controller that should be executed::
+This event is dispatched after the controller to be executed has been resolved
+but before executing it. It's useful to initialize things later needed by the
+controller, such as `param converters`_, and even to change the controller
+entirely::
 
     use Symfony\Component\HttpKernel\Event\FilterControllerEvent;
 
     public function onKernelController(FilterControllerEvent $event)
     {
-        $controller = $event->getController();
         // ...
 
         // the controller can be changed to any PHP callable
-        $event->setController($controller);
+        $event->setController($myCustomController);
     }
 
 .. seealso::
 
     Read more on the :ref:`kernel.controller event <component-http-kernel-kernel-controller>`.
 
-This is the built-in Symfony listener related to this event:
+Execute this command to find out which listeners are registered for this event and
+their priorities:
+
+.. code-block:: terminal
 
-==============================================================================  ========
-Listener Class Name                                                             Priority
-==============================================================================  ========
-:class:`Symfony\\Bundle\\FrameworkBundle\\DataCollector\\RequestDataCollector`  0
-==============================================================================  ========
+    $ php bin/console debug:event-dispatcher kernel.controller
 
 ``kernel.view``
 ~~~~~~~~~~~~~~~
 
 **Event Class**: :class:`Symfony\\Component\\HttpKernel\\Event\\GetResponseForControllerResultEvent`
 
-This event is not used by the FrameworkBundle, but it can be used to implement
-a view sub-system. This event is called *only* if the Controller does *not*
-return a ``Response`` object. The purpose of the event is to allow some
-other return value to be converted into a ``Response``.
-
-The value returned by the Controller is accessible via the ``getControllerResult()``
-method::
+This event is dispatched after the controller has been executed but *only* if
+the controller does *not* return a :class:`Symfony\\Component\\HttpFoundation\\Response`
+object. It's useful to transform the returned value (e.g. a string with some
+HTML contents) into the ``Response`` object needed by Symfony::
 
     use Symfony\Component\HttpKernel\Event\GetResponseForControllerResultEvent;
     use Symfony\Component\HttpFoundation\Response;
@@ -110,13 +103,21 @@ method::
 
     Read more on the :ref:`kernel.view event <component-http-kernel-kernel-view>`.
 
+Execute this command to find out which listeners are registered for this event and
+their priorities:
+
+.. code-block:: terminal
+
+    $ php bin/console debug:event-dispatcher kernel.view
+
 ``kernel.response``
 ~~~~~~~~~~~~~~~~~~~
 
 **Event Class**: :class:`Symfony\\Component\\HttpKernel\\Event\\FilterResponseEvent`
 
-The purpose of this event is to allow other systems to modify or replace
-the ``Response`` object after its creation::
+This event is dispatched after the controller or any ``kernel.view`` listener
+returns a ``Response`` object. It's useful to modify or replace the response
+before sending it back (e.g. add/modify HTTP headers, add cookies, etc.)::
 
     public function onKernelResponse(FilterResponseEvent $event)
     {
@@ -125,91 +126,64 @@ the ``Response`` object after its creation::
         // ... modify the response object
     }
 
-The FrameworkBundle registers several listeners:
-
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\ProfilerListener`
-    Collects data for the current request.
-
-:class:`Symfony\\Bundle\\WebProfilerBundle\\EventListener\\WebDebugToolbarListener`
-    Injects the Web Debug Toolbar.
-
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\ResponseListener`
-    Fixes the Response ``Content-Type`` based on the request format.
-
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\EsiListener`
-    Adds a ``Surrogate-Control`` HTTP header when the Response needs to
-    be parsed for ESI tags.
-
 .. seealso::
 
     Read more on the :ref:`kernel.response event <component-http-kernel-kernel-response>`.
 
-These are the built-in Symfony listeners registered to this event:
-
-===================================================================================  ========
-Listener Class Name                                                                  Priority
-===================================================================================  ========
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\EsiListener`                  0
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\ResponseListener`             0
-:class:`Symfony\\Component\\Security\\Http\\RememberMe\\ResponseListener`            0
-:class:`Symfony\\Bundle\\FrameworkBundle\\DataCollector\\RequestDataCollector`       0
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\ProfilerListener`             -100
-:class:`Symfony\\Bundle\\FrameworkBundle\\EventListener\\TestSessionListener`        -128
-:class:`Symfony\\Bundle\\WebProfilerBundle\\EventListener\\WebDebugToolbarListener`  -128
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\StreamedResponseListener`     -1024
-===================================================================================  ========
+Execute this command to find out which listeners are registered for this event and
+their priorities:
+
+.. code-block:: terminal
+
+    $ php bin/console debug:event-dispatcher kernel.response
 
 ``kernel.finish_request``
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
 **Event Class**: :class:`Symfony\\Component\\HttpKernel\\Event\\FinishRequestEvent`
 
-The purpose of this event is to allow you to reset the global and environmental
-state of the application after a sub-request has finished (for example, the
-translator listener resets the translator's locale to the one of the parent
-request)::
+This event is dispatched after a :ref:`sub request <http-kernel-sub-requests>`
+has finished. It's useful to reset the global state of the application (for
+example, the translator listener resets the translator's locale to the one of
+the parent request)::
 
     public function onKernelFinishRequest(FinishRequestEvent $event)
     {
         if (null === $parentRequest = $this->requestStack->getParentRequest()) {
             return;
         }
 
-        //Reset the locale of the subrequest to the locale of the parent request
+        // Reset the locale of the subrequest to the locale of the parent request
         $this->setLocale($parentRequest);
     }
 
-These are the built-in Symfony listeners related to this event:
+Execute this command to find out which listeners are registered for this event and
+their priorities:
 
-==========================================================================  ========
-Listener Class Name                                                         Priority
-==========================================================================  ========
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\LocaleListener`      0
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\TranslatorListener`  0
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\RouterListener`      0
-:class:`Symfony\\Component\\Security\\Http\\Firewall`                       0
-==========================================================================  ========
+.. code-block:: terminal
+
+    $ php bin/console debug:event-dispatcher kernel.finish_request
 
 ``kernel.terminate``
 ~~~~~~~~~~~~~~~~~~~~
 
 **Event Class**: :class:`Symfony\\Component\\HttpKernel\\Event\\PostResponseEvent`
 
-The purpose of this event is to perform tasks after the response was already
-served to the client.
+This event is dispatched after the response has been sent (after the execution
+of the :method:`Symfony\\Component\\HttpKernel\\HttpKernel::handle` method).
+It's useful to perform slow or complex tasks that don't need to be completed to
+send the response (e.g. sending emails).
 
 .. seealso::
 
     Read more on the :ref:`kernel.terminate event <component-http-kernel-kernel-terminate>`.
 
-This is the built-in Symfony listener related to this event:
+Execute this command to find out which listeners are registered for this event and
+their priorities:
 
-=========================================================================  ========
-Listener Class Name                                                        Priority
-=========================================================================  ========
-`EmailSenderListener`_                                                     0
-=========================================================================  ========
+.. code-block:: terminal
 
+    $ php bin/console debug:event-dispatcher kernel.terminate
 
 .. _kernel-kernel.exception:
 
@@ -218,12 +192,9 @@ Listener Class Name                                                        Prior
 
 **Event Class**: :class:`Symfony\\Component\\HttpKernel\\Event\\GetResponseForExceptionEvent`
 
-The TwigBundle registers an :class:`Symfony\\Component\\HttpKernel\\EventListener\\ExceptionListener`
-that forwards the ``Request`` to a given controller defined by the
-``exception_listener.controller`` parameter.
-
-A listener on this event can create and set a ``Response`` object, create
-and set a new ``Exception`` object, or do nothing::
+This event is dispatched as soon as an error occurs during the handling of the
+HTTP request. It's useful to recover from errors or modify the exception details
+sent as response::
 
     use Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent;
     use Symfony\Component\HttpFoundation\Response;
@@ -240,6 +211,12 @@ and set a new ``Exception`` object, or do nothing::
         // $event->setException($exception);
     }
 
+.. note::
+
+    The TwigBundle registers an :class:`Symfony\\Component\\HttpKernel\\EventListener\\ExceptionListener`
+    that forwards the ``Request`` to a given controller defined by the
+    ``exception_listener.controller`` parameter.
+
 .. note::
 
     Symfony uses the following logic to determine the HTTP status code of the
@@ -261,13 +238,11 @@ and set a new ``Exception`` object, or do nothing::
 
     Read more on the :ref:`kernel.exception event <component-http-kernel-kernel-exception>`.
 
-These are the built-in Symfony listeners registered to this event:
+Execute this command to find out which listeners are registered for this event and
+their priorities:
+
+.. code-block:: terminal
 
-=========================================================================  ========
-Listener Class Name                                                        Priority
-=========================================================================  ========
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\ProfilerListener`   0
-:class:`Symfony\\Component\\HttpKernel\\EventListener\\ExceptionListener`  -128
-=========================================================================  ========
+    $ php bin/console debug:event-dispatcher kernel.exception
 
-.. _`EmailSenderListener`: https://github.com/symfony/swiftmailer-bundle/blob/master/EventListener/EmailSenderListener.php
+.. _`param converters`: https://symfony.com/doc/master/bundles/SensioFrameworkExtraBundle/annotations/converters.html