Merge remote-tracking branch 'upstream/7.0' into 7.0

* upstream/7.0:
  -
  [Console] Add more examples for lazy commands
  [Reference] Fix assets links have wrong label
  some tweaks for the Webhook docs
  fix headline
  [Security] Update request matcher doc

Author: javiereguiluz

console/commands_as_services.rst

@@ -133,3 +133,5 @@ only when the ``app:sunshine`` command is actually called.
 .. caution::
 
     Calling the ``list`` command will instantiate all commands, including lazy commands.
+    However, if the command is a ``Symfony\Component\Console\Command\LazyCommand``, then
+    the underlying command factory will not be executed.

console/lazy_commands.rst

@@ -10,6 +10,13 @@ The traditional way of adding commands to your application is to use
 :method:`Symfony\\Component\\Console\\Application::add`, which expects a
 ``Command`` instance as an argument.
 
+This approach can have downsides as some commands might be expensive to
+instantiate in which case you may want to lazy-load them. Note however that lazy-loading
+is not absolute. Indeed a few commands such as `list`, `help` or `_complete` can
+require to instantiate other commands although they are lazy. For example `list` needs
+to get the name and description of all commands, which might require the command to be
+instantiated to get.
+
 In order to lazy-load commands, you need to register an intermediate loader
 which will be responsible for returning ``Command`` instances::
 
@@ -19,7 +26,9 @@ which will be responsible for returning ``Command`` instances::
     use Symfony\Component\Console\CommandLoader\FactoryCommandLoader;
 
     $commandLoader = new FactoryCommandLoader([
-        'app:heavy' => function (): Command { return new HeavyCommand(); },
+        // Note that the `list` command will still instantiate that command
+        // in this example.
+        'app:heavy' => static fn(): Command => new HeavyCommand(),
     ]);
 
     $application = new Application();
@@ -36,6 +45,28 @@ method accepts any
 :class:`Symfony\\Component\\Console\\CommandLoader\\CommandLoaderInterface`
 instance so you can use your own implementation.
 
+Another way to do so is to take advantage of ``Symfony\Component\Console\Command\LazyCommand``::
+
+    use App\Command\HeavyCommand;
+    use Symfony\Component\Console\Application;
+    use Symfony\Component\Console\Command\Command;
+    use Symfony\Component\Console\CommandLoader\FactoryCommandLoader;
+
+    // In this case although the command is instantiated, the underlying command factory
+    // will not be executed unless the command is actually executed or one tries to access
+    // to its input definition to know its argument or option inputs.
+    $lazyCommand = new LazyCommand(
+        'app:heavy',
+        [],
+        'This is another more complete form of lazy command.',
+        false,
+        static fn (): Command => new HeavyCommand(),
+    );
+
+    $application = new Application();
+    $application->add($lazyCommand);
+    $application->run();
+
 Built-in Command Loaders
 ------------------------
 

mailer.rst

@@ -272,7 +272,7 @@ party provider:
 
 .. tip::
 
-    Some third party mailers, when using the API, support status callback
+    Some third party mailers, when using the API, support status callbacks
     via webhooks. See the :doc:`Webhook documentation </webhook>` for more
     details.
 

messenger.rst

@@ -881,7 +881,7 @@ running the ``messenger:consume`` command.
 
 .. _messenger-retries-failures:
 
-Rate limited transport
+Rate Limited Transport
 ~~~~~~~~~~~~~~~~~~~~~~
 
 Sometimes you might need to rate limit your message worker. You can configure a

notifier.rst

@@ -104,7 +104,7 @@ Service             Package                                DSN
 
 .. tip::
 
-    Some third party transports, when using the API, support status callback
+    Some third party transports, when using the API, support status callbacks
     via webhooks. See the :doc:`Webhook documentation </webhook>` for more
     details.
 

reference/twig_reference.rst

@@ -116,8 +116,10 @@ the application is installed (e.g. in case the project is accessed in a host
 subdirectory) and the optional asset package base path.
 
 Symfony provides various cache busting implementations via the
-:ref:`reference-framework-assets-version`, :ref:`reference-assets-version-strategy`,
-and :ref:`reference-assets-json-manifest-path` configuration options.
+:ref:`assets.version <reference-framework-assets-version>`,
+:ref:`assets.version_strategy <reference-assets-version-strategy>`,
+and :ref:`assets.json_manifest_path <reference-assets-json-manifest-path>`
+configuration options.
 
 .. seealso::
 

security/access_control.rst

@@ -19,10 +19,10 @@ things:
 1. Matching Options
 -------------------
 
-Symfony creates an instance of :class:`Symfony\\Component\\HttpFoundation\\RequestMatcher`
-for each ``access_control`` entry, which determines whether or not a given
-access control should be used on this request. The following ``access_control``
-options are used for matching:
+Symfony uses :class:`Symfony\\Component\\HttpFoundation\\ChainRequestMatcher` for
+each ``access_control`` entry, which determines which implementation of
+:class:`Symfony\\Component\\HttpFoundation\\RequestMatcherInterface` should be used
+on this request. The following ``access_control`` options are used for matching:
 
 * ``path``: a regular expression (without delimiters)
 * ``ip`` or ``ips``: netmasks are also supported (can be a comma-separated string)

webhook.rst

@@ -12,17 +12,17 @@ Installation
 
     $ composer require symfony/webhook
 
-Usage in combination with the Mailer component
+Usage in Combination with the Mailer Component
 ----------------------------------------------
 
 When using a third-party mailer, you can use the Webhook component to receive
 webhook calls from the third-party mailer.
 
-In this example Mailgun is used with ``'mailer_mailgun'`` as webhook type.
-Any type name can be used as long as it's unique. Make sure to use it in the
+In this example Mailgun is used with ``'mailer_mailgun'`` as the webhook type.
+Any type name can be used as long as it is unique. Make sure to use it in the
 routing configuration, the webhook URL and the RemoteEvent consumer.
 
-Install the third party mailer as described in the documentation of the
+Install the third-party mailer as described in the documentation of the
 :ref:`Mailer component <mailer_3rd_party_transport>`.
 
 The Webhook component routing needs to be defined:
@@ -130,13 +130,13 @@ With this done, you can now add a RemoteEvent consumer to react to the webhooks:
         }
     }
 
-Usage in combination with the Notifier component
+Usage in Combination with the Notifier Component
 ------------------------------------------------
 
 The usage of the Webhook component when using a third-party transport in
 the Notifier is very similar to the usage with the Mailer.
 
-Currently, the following third-party sms transports support webhooks:
+Currently, the following third-party SMS transports support webhooks:
 
 ============ ==========================================
 SMS service  Parser service name