Merge branch '6.4' into 7.0

* 6.4:
  fix(doc): typo
  Tweaks
  [Validator] Advanced Validation Group Provider
  Minor formating
  Reword
  Renaming W3C to HTML5...
  Minor tweak
  Tweaks
  Add note about indexing config classes
  [DI] Add note about testing service locators
  tip to not follow redirects when testing mailer
  link symfony default style on coloring documentation

Author: OskarStark

configuration.rst

@@ -1283,6 +1283,12 @@ namespace ``Symfony\Config``::
     Nested configs (e.g. ``\Symfony\Config\Framework\CacheConfig``) are regular
     PHP objects which aren't autowired when using them as an argument type.
 
+.. note::
+
+    In order to get ConfigBuilders autocompletion in your IDE/editor, make sure
+    to not exclude the directory where these classes are generated (by default,
+    in ``var/cache/dev/Symfony/Config/``).
+
 Keep Going!
 -----------
 

console/coloring.rst

@@ -1,8 +1,10 @@
 How to Color and Style the Console Output
 =========================================
 
-By using colors in the command output, you can distinguish different types of
-output (e.g. important messages, titles, comments, etc.).
+Symfony provides an optional :doc:`console style </console/style>` to render the
+input and output of commands in a consistent way. If you prefer to apply your
+own style, use the utilities explained in this article to show colors in the command
+output (e.g. to differentiate between important messages, titles, comments, etc.).
 
 .. note::
 

frontend/asset_mapper.rst

@@ -17,7 +17,7 @@ The AssetMapper component has two main features:
 * :ref:`Importmaps <importmaps-javascript>`: A native browser feature that makes it easier
   to use the JavaScript ``import`` statement (e.g. ``import { Modal } from 'bootstrap'``)
   without a build system. It's supported in all browsers (thanks to a shim)
-  and is a `W3C standard <https://html.spec.whatwg.org/multipage/webappapis.html#import-maps>`_.
+  and is part of the `HTML5 standard <https://html.spec.whatwg.org/multipage/webappapis.html#import-maps>`_.
 
 Installation
 ------------
@@ -80,15 +80,16 @@ the file, the version part of the URL will change automatically!
 Serving Assets in dev vs prod
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-In the ``dev`` environment, the URL - ``/assets/images/duck-3c16d9220694c0e56d8648f25e6035e9.png``
-is handled and returned by your Symfony app. For the ``prod`` environment, before
-deploy, you should run:
+In the ``dev`` environment, the URL ``/assets/images/duck-3c16d9220694c0e56d8648f25e6035e9.png``
+is handled and returned by your Symfony app.
+
+For the ``prod`` environment, before deploy, you should run:
 
 .. code-block:: terminal
 
     $ php bin/console asset-map:compile
 
-This will physically copy all the files from your mapped directories into
+This will physically copy all the files from your mapped directories to
 ``public/assets/`` so that they're served directly by your web server.
 See :ref:`Deployment <asset-mapper-deployment>` for more details.
 

mailer.rst

@@ -1807,6 +1807,13 @@ the :class:`Symfony\\Bundle\\FrameworkBundle\\Test\\MailerAssertionsTrait`::
         }
     }
 
+.. tip::
+
+   If your controller returns a redirect response after sending the email, make
+   sure to have your client *not* follow redirects. The kernel is rebooted after
+   following the redirection and the message will be lost from the mailer event
+   handler.
+
 .. _`Amazon SES`: https://github.com/symfony/symfony/blob/{version}/src/Symfony/Component/Mailer/Bridge/Amazon/README.md
 .. _`App Password`: https://support.google.com/accounts/answer/185833
 .. _`Brevo`: https://github.com/symfony/symfony/blob/{version}/src/Symfony/Component/Mailer/Bridge/Brevo/README.md

security/remember_me.rst

@@ -235,7 +235,7 @@ present:
 .. image:: /_images/security/profiler-badges.png
     :alt: The Security page of the Symfony profiler, with the "Authenticators" tab showing the remember me badge in the passport object.
 
-Without this badge, remember me will be not be activated (regardless of all
+Without this badge, remember me will not be activated (regardless of all
 other settings).
 
 Add Remember Me Support to Custom Authenticators

service_container/service_subscribers_locators.rst

@@ -1004,6 +1004,15 @@ To unit test a service subscriber, you can create a fake container::
     $serviceSubscriber = new MyService($container);
     // ...
 
+.. note::
+
+    When defining the service locator like this, beware that the
+    :method:`Symfony\\Contracts\\Service\\ServiceLocatorTrait::getProvidedServices`
+    of your container will use the return type of the closures as the values of the
+    returned array. If no return type is defined, the value will be ``?``. If you
+    want the values to reflect the classes of your services, the return type has
+    to be set on your closures.
+
 Another alternative is to mock it using ``PHPUnit``::
 
     use Psr\Container\ContainerInterface;

validation/sequence_provider.rst

@@ -344,6 +344,95 @@ provides a sequence of groups to be validated:
             }
         }
 
+Advanced Validation Group Provider
+----------------------------------
+
+In the previous section, you learned how to change the sequence of groups
+dynamically based on the state of your entity. However, in more advanced cases
+you might need to use some external configuration or service to define that
+sequence of groups.
+
+Managing the entity initialization and manually setting its dependencies can
+be cumbersome, and the implementation might not align with the entity
+responsibilities. To solve this, you can configure the implementation of the
+:class:`Symfony\\Component\\Validator\\GroupProviderInterface` outside of the
+entity, and even register the group provider as a service.
+
+Here's how you can achieve this:
+
+ 1) **Define a Separate Group Provider Class:** create a class that implements
+    the :class:`Symfony\\Component\\Validator\\GroupProviderInterface`
+    and handles the dynamic group sequence logic;
+ 2) **Configure the User with the Provider:** use the ``provider`` option within
+    the :class:`Symfony\\Component\\Validator\\Constraints\\GroupSequenceProvider`
+    attribute to link the entity with the provider class;
+ 3) **Autowiring or Manual Tagging:** if :doc:` autowiring </service_container/autowiring>`
+    is enabled, your custom provider will be automatically linked. Otherwise, you must
+    :doc:`tag your service </service_container/tags>` manually with the ``validator.group_provider`` tag.
+
+.. configuration-block::
+
+    .. code-block:: php-attributes
+
+        // src/Entity/User.php
+        namespace App\Entity;
+
+        // ...
+        use App\Validator\UserGroupProvider;
+
+        #[Assert\GroupSequenceProvider(provider: UserGroupProvider::class)]
+        class User
+        {
+            // ...
+        }
+
+    .. code-block:: yaml
+
+        # config/validator/validation.yaml
+        App\Entity\User:
+            group_sequence_provider: App\Validator\UserGroupProvider
+
+    .. code-block:: xml
+
+        <!-- config/validator/validation.xml -->
+        <?xml version="1.0" encoding="UTF-8" ?>
+        <constraint-mapping xmlns="http://symfony.com/schema/dic/constraint-mapping"
+            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+            xsi:schemaLocation="http://symfony.com/schema/dic/constraint-mapping
+                https://symfony.com/schema/dic/constraint-mapping/constraint-mapping-1.0.xsd">
+
+            <class name="App\Entity\User">
+                <group-sequence-provider>
+                    <value>App\Validator\UserGroupProvider</value>
+                </group-sequence-provider>
+                <!-- ... -->
+            </class>
+        </constraint-mapping>
+
+    .. code-block:: php
+
+        // src/Entity/User.php
+        namespace App\Entity;
+
+        // ...
+        use App\Validator\UserGroupProvider;
+        use Symfony\Component\Validator\Mapping\ClassMetadata;
+
+        class User
+        {
+            // ...
+
+            public static function loadValidatorMetadata(ClassMetadata $metadata): void
+            {
+                $metadata->setGroupProvider(UserGroupProvider::class);
+                $metadata->setGroupSequenceProvider(true);
+                // ...
+            }
+        }
+
+With this approach, you can maintain a clean separation between the entity
+structure and the group sequence logic, allowing for more advanced use cases.
+
 How to Sequentially Apply Constraints on a Single Property
 ----------------------------------------------------------