Merge branch '4.1' into 4.2

javiereguiluz · javiereguiluz · commit f4b9666f6078 · 2019-01-18T12:34:06.000+01:00
* 4.1:
  Update installation.rst
  remove Symfony 2/3 versionadded directives
  remove Symfony 2.8 versionadded directive
  Removed a small article about console logging
  Describe things more precisely
diff --git a/_build/redirection_map b/_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
diff --git a/components/console/events.rst b/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
 --------------------------------------
 
diff --git a/components/serializer.rst b/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
diff --git a/components/validator.rst b/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
 -------------------------------
 
diff --git a/configuration/external_parameters.rst b/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
diff --git a/console.rst b/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
 ----------
 
diff --git a/console/request_context.rst b/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
 -------------------------------------------
 
diff --git a/frontend/encore/installation.rst b/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
diff --git a/reference/configuration/framework.rst b/reference/configuration/framework.rst
@@ -1647,10 +1647,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
diff --git a/reference/forms/types/number.rst b/reference/forms/types/number.rst
@@ -46,11 +46,6 @@ Field Options
 scale
 ~~~~~
 
-.. versionadded:: 2.7
-
-    The ``scale`` option was introduced in Symfony 2.7. Prior to Symfony 2.7,
-    it was known as ``precision``.
-
 **type**: ``integer`` **default**: Locale-specific (usually around ``3``)
 
 This specifies how many decimals will be allowed until the field rounds
diff --git a/service_container/alias_private.rst b/service_container/alias_private.rst
@@ -153,10 +153,6 @@ Anonymous Services
 
     Anonymous services are only supported by the XML and YAML configuration formats.
 
-.. versionadded:: 3.3
-
-    The feature to configure anonymous services in YAML was introduced in Symfony 3.3.
-
 In some cases, you may want to prevent a service being used as a dependency of
 other services. This can be achieved by creating an anonymous service. These
 services are like regular services but they don't define an ID and they are
diff --git a/service_container/autowiring.rst b/service_container/autowiring.rst
@@ -338,9 +338,10 @@ dealing with the ``TransformerInterface``.
 
 .. tip::
 
-    As long as there is only one class implementing the interface and that class
-    is part of the same namespace configuring the alias is not mandatory and Symfony
-    will automatically create one.
+    When using a `service definition prototype`_, if only one service is
+    discovered that implements an interface, and that interface is also
+    discovered at the same time, configuring the alias is not mandatory
+    and Symfony will automatically create one.
 
 Dealing with Multiple Implementations of the Same Type
 ------------------------------------------------------
@@ -500,3 +501,4 @@ Public bundles should explicitly configure their services and not rely on autowi
 
 .. _Rapid Application Development: https://en.wikipedia.org/wiki/Rapid_application_development
 .. _ROT13: https://en.wikipedia.org/wiki/ROT13
+.. _service definition prototype: https://symfony.com/blog/new-in-symfony-3-3-psr-4-based-service-discovery
diff --git a/service_container/service_subscribers_locators.rst b/service_container/service_subscribers_locators.rst
@@ -4,10 +4,6 @@
 Service Subscribers & Locators
 ==============================
 
-.. versionadded:: 3.3
-
-    Service subscribers and locators were introduced in Symfony 3.3.
-
 Sometimes, a service needs access to several other services without being sure
 that all of them will actually be used. In those cases, you may want the
 instantiation of the services to be lazy. However, that's not possible using
diff --git a/testing.rst b/testing.rst
@@ -593,10 +593,6 @@ will no longer be followed::
 Reporting Exceptions
 ~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 3.4
-
-    The ``catchExceptions()`` method was introduced in Symfony 3.4.
-
 Debugging exceptions in functional tests may be difficult because by default
 they are caught and you need to look at the logs to see which exception was
 thrown. Disabling catching of exceptions in the test client allows the exception

Original file line number	Diff line number	Diff line change
`@@ -64,10 +64,6 @@ If you have lots of validation errors, you can filter them by error code::`
`64`	`64`	`// handle this specific error (display some message, send an email, etc.)`
`65`	`65`	`}`
`66`	`66`
`67`		`-.. versionadded:: 3.3`
`68`		`-`
`69`		- The ``findByCodes()`` method was introduced in Symfony 3.3.
`70`		`-`
`71`	`67`	`Retrieving a Validator Instance`
`72`	`68`	`-------------------------------`
`73`	`69`