Merge branch '4.2'

* 4.2:
  Update installation.rst
  remove Symfony 2/3 versionadded directives
  remove Symfony 2.8 versionadded directive
  drop not needed configuration block
  Removed a small article about console logging
  Describe things more precisely

Author: javiereguiluz

_build/redirection_map

@@ -119,7 +119,7 @@
 /cookbook/console/commands_as_services /console/commands_as_services
 /cookbook/console/console_command /console
 /cookbook/console/index /console
-/cookbook/console/logging /console/logging
+/cookbook/console/logging /console
 /cookbook/console/request_context /console/request_context
 /cookbook/console/style /console/style
 /cookbook/console/usage /console
@@ -402,3 +402,4 @@
 /components/weblink /components/web_link
 /frontend/encore/installation-no-flex /frontend/encore/installation
 /http_cache/form_csrf_caching /security/csrf
+/console/logging /console

components/console/events.rst

@@ -114,6 +114,8 @@ Listeners receive a
         $event->setError(new \LogicException('Caught exception', $exitCode, $event->getError()));
     });
 
+.. _console-events-terminate:
+
 The ``ConsoleEvents::TERMINATE`` Event
 --------------------------------------
 

components/serializer.rst

@@ -166,11 +166,6 @@ needs three parameters:
 #. The name of the class this information will be decoded to
 #. The encoder used to convert that information into an array
 
-.. versionadded:: 3.3
-
-    Support for the ``allow_extra_attributes`` key in the context was introduced
-    in Symfony 3.3.
-
 By default, additional attributes that are not mapped to the denormalized object
 will be ignored by the Serializer component. If you prefer to throw an exception
 when this happens, set the ``allow_extra_attributes`` context option to

components/validator.rst

@@ -64,10 +64,6 @@ If you have lots of validation errors, you can filter them by error code::
         // handle this specific error (display some message, send an email, etc.)
     }
 
-.. versionadded:: 3.3
-
-    The ``findByCodes()`` method was introduced in Symfony 3.3.
-
 Retrieving a Validator Instance
 -------------------------------
 

configuration/external_parameters.rst

@@ -137,10 +137,6 @@ the following:
 Environment Variable Processors
 -------------------------------
 
-.. versionadded:: 3.4
-
-    Environment variable processors were introduced in Symfony 3.4.
-
 The values of environment variables are considered strings by default.
 However, your code may expect other data types, like integers or booleans.
 Symfony solves this problem with *processors*, which modify the contents of the

console.rst

@@ -366,6 +366,15 @@ console::
     :class:`Symfony\\Component\\Console\\Application <Symfony\\Component\\Console\\Application>`
     and extend the normal ``\PHPUnit\Framework\TestCase``.
 
+Logging Command Errors
+----------------------
+
+Whenever an exception is thrown while running commands, Symfony adds a log
+message for it including the entire failing command. In addition, Symfony
+registers an :doc:`event subscriber </event_dispatcher>` to listen to the
+:ref:`ConsoleEvents::TERMINATE event <console-events-terminate>` and adds a log
+message whenever a command doesn't finish with the ``0`` exit status.
+
 Learn More
 ----------
 

console/request_context.rst

@@ -65,10 +65,6 @@ will override the defaults.
         $container->setParameter('asset.request_context.base_path', $container->getParameter('router.request_context.base_url'));
         $container->setParameter('asset.request_context.secure', true);
 
-.. versionadded:: 3.4
-
-    The ``asset.request_context.*`` parameters were introduced in Symfony 3.4.
-
 Configuring the Request Context per Command
 -------------------------------------------
 

frontend/encore/installation.rst

@@ -57,7 +57,7 @@ is the main config file for both Webpack and Webpack Encore:
 
     Encore
         // directory where compiled assets will be stored
-        .setOutputPath('web/build/')
+        .setOutputPath('public/build/')
         // public path used by the web server to access the output path
         .setPublicPath('/build')
         // only needed for CDN's or sub-directory deploy

messenger/handler_results.rst

@@ -6,23 +6,19 @@ Getting Results from your Handler
 
 When a message is handled, the :class:`Symfony\\Component\\Messenger\\Middleware\\HandleMessageMiddleware`
 adds a :class:`Symfony\\Component\\Messenger\\Stamp\\HandledStamp` for each object that handled the message.
-You can use this to get the value returned by the handler(s):
+You can use this to get the value returned by the handler(s)::
 
-.. configuration-block::
+    use Symfony\Component\Messenger\MessageBusInterface;
+    use Symfony\Component\Messenger\Stamp\HandledStamp;
 
-    .. code-block:: php
+    $envelope = $messageBus->dispatch(SomeMessage());
 
-        use Symfony\Component\Messenger\MessageBusInterface;
-        use Symfony\Component\Messenger\Stamp\HandledStamp;
+    // get the value that was returned by the last message handler
+    $handledStamp = $envelope->last(HandledStamp::class);
+    $handledStamp->getResult();
 
-        $envelope = $messageBus->dispatch(SomeMessage());
-
-        // get the value that was returned by the last message handler
-        $handledStamp = $envelope->last(HandledStamp::class);
-        $handledStamp->getResult();
-
-        // or get info about all of handlers
-        $handledStamps = $envelope->all(HandledStamp::class);
+    // or get info about all of handlers
+    $handledStamps = $envelope->all(HandledStamp::class);
 
 A :class:`Symfony\\Component\\Messenger\\HandleTrait` also exists in order to ease
 leveraging a Messenger bus for synchronous needs.
@@ -41,77 +37,69 @@ As queries are usually synchronous and expected to be handled once,
 getting the result from the handler is a common need.
 
 To make this easy, you can leverage the ``HandleTrait`` in any class that has
-a ``$messageBus`` property:
+a ``$messageBus`` property::
+
+    // src/Action/ListItems.php
+    namespace App\Action;
 
-.. configuration-block::
+    use App\Message\ListItemsQuery;
+    use App\MessageHandler\ListItemsQueryResult;
+    use Symfony\Component\Messenger\HandleTrait;
+    use Symfony\Component\Messenger\MessageBusInterface;
 
-    .. code-block:: php
+    class ListItems
+    {
+        use HandleTrait;
+
+        public function __construct(MessageBusInterface $messageBus)
+        {
+            $this->messageBus = $messageBus;
+        }
 
-        // src/Action/ListItems.php
-        namespace App\Action;
+        public function __invoke()
+        {
+            $result = $this->query(new ListItemsQuery(/* ... */));
 
-        use App\Message\ListItemsQuery;
-        use App\MessageHandler\ListItemsQueryResult;
-        use Symfony\Component\Messenger\HandleTrait;
-        use Symfony\Component\Messenger\MessageBusInterface;
+            // Do something with the result
+            // ...
+        }
 
-        class ListItems
+        // Creating such a method is optional, but allows type-hinting the result
+        private function query(ListItemsQuery $query): ListItemsResult
         {
-            use HandleTrait;
-
-            public function __construct(MessageBusInterface $messageBus)
-            {
-                $this->messageBus = $messageBus;
-            }
-
-            public function __invoke()
-            {
-                $result = $this->query(new ListItemsQuery(/* ... */));
-
-                // Do something with the result
-                // ...
-            }
-
-            // Creating such a method is optional, but allows type-hinting the result
-            private function query(ListItemsQuery $query): ListItemsResult
-            {
-                return $this->handle($query);
-            }
+            return $this->handle($query);
         }
+    }
 
 Hence, you can use the trait to create command & query bus classes.
 For example, you could create a special ``QueryBus`` class and inject it
-wherever you need a query bus behavior instead of the ``MessageBusInterface``:
+wherever you need a query bus behavior instead of the ``MessageBusInterface``::
 
-.. configuration-block::
+    // src/MessageBus/QueryBus.php
+    namespace App\MessageBus;
 
-    .. code-block:: php
+    use Symfony\Component\Messenger\Envelope;
+    use Symfony\Component\Messenger\HandleTrait;
+    use Symfony\Component\Messenger\MessageBusInterface;
 
-        // src/MessageBus/QueryBus.php
-        namespace App\MessageBus;
+    class QueryBus
+    {
+        use HandleTrait;
 
-        use Symfony\Component\Messenger\Envelope;
-        use Symfony\Component\Messenger\HandleTrait;
-        use Symfony\Component\Messenger\MessageBusInterface;
+        public function __construct(MessageBusInterface $messageBus)
+        {
+            $this->messageBus = $messageBus;
+        }
 
-        class QueryBus
+        /**
+         * @param object|Envelope $query
+         *
+         * @return mixed The handler returned value
+         */
+        public function query($query)
         {
-            use HandleTrait;
-
-            public function __construct(MessageBusInterface $messageBus)
-            {
-                $this->messageBus = $messageBus;
-            }
-
-            /**
-             * @param object|Envelope $query
-             *
-             * @return mixed The handler returned value
-             */
-            public function query($query)
-            {
-                return $this->handle($query);
-            }
+            return $this->handle($query);
         }
+    }
 
 .. _`article about CQRS`: https://martinfowler.com/bliki/CQRS.html

reference/configuration/framework.rst

@@ -1638,10 +1638,6 @@ for translation files.
 default_path
 ............
 
-.. versionadded:: 3.4
-
-    The ``default_path`` option was introduced in Symfony 3.4.
-
 **type**: ``string`` **default**: ``%kernel.project_dir%/translations``
 
 This option allows to define the path where the application translations files