Merge branch '6.0' into 6.1

* 6.0:
  Add information about strict_mode for encore
  [Security] Added a note regarding the loginUser() method
  Note that env vars are not always compatible with options
  Update autowiring.rst
  Explaining how to inject the form factory

Author: javiereguiluz

components/form.rst

@@ -371,10 +371,6 @@ you need to. If your application uses global or static variables (not usually a
 good idea), then you can store the object on some static class or do something
 similar.
 
-Regardless of how you architect your application, remember that you
-should only have one form factory and that you'll need to be able to access
-it throughout your application.
-
 .. _component-form-intro-create-simple-form:
 
 Creating a simple Form
@@ -383,7 +379,8 @@ Creating a simple Form
 .. tip::
 
     If you're using the Symfony Framework, then the form factory is available
-    automatically as a service called ``form.factory``. Also, the default
+    automatically as a service called ``form.factory``, you can inject it as
+    ``Symfony\Component\Form\FormFactoryInterface``. Also, the default
     base controller class has a :method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\AbstractController::createFormBuilder`
     method, which is a shortcut to fetch the form factory and call ``createBuilder()``
     on it.

configuration.rst

@@ -571,9 +571,10 @@ configure options that depend on where the application is run (e.g. the database
 credentials are usually different in production versus your local machine). If
 the values are sensitive, you can even :doc:`encrypt them as secrets </configuration/secrets>`.
 
-You can reference environment variables using the special syntax
-``%env(ENV_VAR_NAME)%``. The values of these options are resolved at runtime
-(only once per request, to not impact performance).
+Use the special syntax ``%env(ENV_VAR_NAME)%`` to reference environment variables.
+The values of these options are resolved at runtime (only once per request, to
+not impact performance) so you can change the application behavior without having
+to clear the cache.
 
 This example shows how you could configure the database connection using an env var:
 
@@ -640,6 +641,14 @@ To define the value of an env var, you have several options:
     Some hosts - like SymfonyCloud - offer easy `utilities to manage env vars`_
     in production.
 
+.. note::
+
+    Some configuration features are not compatible with env vars. For example,
+    defining some container parameters conditionally based on the existence of
+    another configuration option. When using an env var, the configuration option
+    always exists, because its value will be ``null`` when the related env var
+    is not defined.
+
 .. caution::
 
     Beware that dumping the contents of the ``$_SERVER`` and ``$_ENV`` variables

frontend/encore/faq.rst

@@ -169,3 +169,28 @@ running it (e.g. when executing ``yarn encore dev``). Fix this issue calling to
     // ... the rest of the Encore configuration
 
 .. _`Webpack integration in PhpStorm`: https://www.jetbrains.com/help/phpstorm/using-webpack.html
+
+My Tests are Failing Because of ``entrypoints.json`` File
+---------------------------------------------------------
+
+After installing Encore, you might see the following error when running tests
+locally or on your Continuous Integration server:
+
+.. code-block:: text
+
+    Uncaught PHP Exception Twig\Error\RuntimeError:
+    "An exception has been thrown during the rendering of a template
+    ("Could not find the entrypoints file from Webpack:
+    the file "/var/www/html/public/build/entrypoints.json" does not exist.
+
+This is happening because you did not build your Encore assets, hence no
+``entrypoints.json`` file. To solve this error, either build Encore assets or
+set the ``strict_mode`` option to ``false`` (this prevents Encore's Twig
+functions to trigger exceptions when there's no ``entrypoints.json`` file):
+
+.. code-block:: yaml
+
+    # config/packages/test/webpack_encore.yaml
+    webpack_encore:
+        strict_mode: false
+        # ...

service_container/autowiring.rst

@@ -369,8 +369,7 @@ dealing with the ``TransformerInterface``.
 .. tip::
 
     When using a `service definition prototype`_, if only one service is
-    discovered that implements an interface, and that interface is also
-    discovered in the same file, configuring the alias is not mandatory
+    discovered that implements an interface, configuring the alias is not mandatory
     and Symfony will automatically create one.
 
 Dealing with Multiple Implementations of the Same Type

testing.rst

@@ -621,6 +621,11 @@ You can pass any
 :class:`Symfony\\Bundle\\FrameworkBundle\\Test\\TestBrowserToken` object and
 stores in the session of the test client.
 
+.. note::
+
+    By design, the ``loginUser()`` method doesn't work when using stateless firewalls.
+    Instead, add the appropriate token/header in each ``request()`` call.
+
 Making AJAX Requests
 ....................