Merge branch '6.2' into 6.3

* 6.2:
  Rename context
  minor
  [Mailer] remove bcc for signed messages
  [Attributes] Add attributes overview
  Update mailer.rst

Author: OskarStark

components/serializer.rst

@@ -232,7 +232,7 @@ data.
 Context
 -------
 
-Many Serializer features can be configured :doc:`using a context </serializer#serializer-context>`.
+Many Serializer features can be configured :doc:`using a context </serializer#serializer_serializer-context>`.
 
 .. _component-serializer-attributes-groups:
 
@@ -432,6 +432,8 @@ If some serialization groups are set, only attributes allowed by those groups ca
 
 As for groups, attributes can be selected during both the serialization and deserialization process.
 
+.. _serializer_ignoring-attributes:
+
 Ignoring Attributes
 -------------------
 
@@ -628,6 +630,8 @@ processes::
     $anne = $normalizer->denormalize(['first_name' => 'Anne'], 'Person');
     // Person object with firstName: 'Anne'
 
+.. _serializer_name-conversion:
+
 Configure name conversion using metadata
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -1193,7 +1197,7 @@ Option          Description                                               Defaul
 Context Builders
 ----------------
 
-Instead of passing plain PHP arrays to the :ref:`serialization context <serializer-context>`,
+Instead of passing plain PHP arrays to the :ref:`serialization context <serializer_serializer-context>`,
 you can use "context builders" to define the context using a fluent interface::
 
     use Symfony\Component\Serializer\Context\Encoder\CsvEncoderContextBuilder;
@@ -1396,6 +1400,8 @@ having unique identifiers::
     var_dump($serializer->serialize($org, 'json'));
     // {"name":"Les-Tilleuls.coop","members":[{"name":"K\u00e9vin", organization: "Les-Tilleuls.coop"}]}
 
+.. _serializer_handling-serialization-depth:
+
 Handling Serialization Depth
 ----------------------------
 
@@ -1693,6 +1699,8 @@ will be thrown. The type enforcement of the properties can be disabled by settin
 the serializer context option ``ObjectNormalizer::DISABLE_TYPE_ENFORCEMENT``
 to ``true``.
 
+.. _serializer_interfaces-and-abstract-classes:
+
 Serializing Interfaces and Abstract Classes
 -------------------------------------------
 

console.rst

@@ -206,6 +206,8 @@ available in the ``configure()`` method::
         }
     }
 
+.. _console_registering-the-command:
+
 Registering the Command
 ~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -533,13 +535,13 @@ call ``setAutoExit(false)`` on it to get the command result in ``CommandTester``
         $application->setAutoExit(false);
 
         $tester = new ApplicationTester($application);
-        
+
 
 .. caution::
 
     When testing ``InputOption::VALUE_NONE`` command options, you must pass an
     empty value to them::
-    
+
         $commandTester = new CommandTester($command);
         $commandTester->execute(['--some-option' => '']);
 

event_dispatcher.rst

@@ -143,6 +143,8 @@ listener class:
        method (which makes event listeners invokable);
     #. If the ``__invoke()`` method is not defined either, throw an exception.
 
+.. _event-dispatcher_event-listener-attributes:
+
 Defining Event Listeners with PHP Attributes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

mailer.rst

@@ -1043,6 +1043,12 @@ using for example OpenSSL or obtained at an official Certificate Authority (CA).
 The email recipient must have the CA certificate in the list of trusted issuers
 in order to verify the signature.
 
+.. caution::
+
+    If you use message signature, sending to ``Bcc`` will be removed from the
+    message. If you need to send a message to multiple recipients, you need
+    to compute a new signature for each recipient.
+
 S/MIME Signer
 .............
 
@@ -1751,7 +1757,7 @@ the :class:`Symfony\\Bundle\\FrameworkBundle\\Test\\MailerAssertionsTrait`::
             $client->request('GET', '/mail/send');
             $this->assertResponseIsSuccessful();
 
-            $this->assertEmailCount(1);
+            $this->assertEmailCount(1); // use assertQueuedEmailCount() when using Messenger
 
             $email = $this->getMailerMessage();
 
@@ -1773,3 +1779,6 @@ the :class:`Symfony\\Bundle\\FrameworkBundle\\Test\\MailerAssertionsTrait`::
 .. _`default_socket_timeout`: https://www.php.net/manual/en/filesystem.configuration.php#ini.default-socket-timeout
 .. _`RFC 3986`: https://www.ietf.org/rfc/rfc3986.txt
 .. _`App Password`: https://support.google.com/accounts/answer/185833
+
+
+

reference/attributes.rst

@@ -0,0 +1,77 @@
+.. index::
+    single: Attributes
+
+Symfony Attributes Overview
+===========================
+
+Attributes are the successor of annotation since PHP 8. Attributes are native
+to the language and Symfony takes full advantage of them across the framework
+ans its different components.
+
+Doctrine Bridge
+~~~~~~~~~~~~~~~
+
+* :doc:`UniqueEntity </reference/constraints/UniqueEntity>`
+
+Command
+~~~~~~~
+
+* :ref:`AsCommand <console_registering-the-command>`
+
+Contracts
+~~~~~~~~~
+
+* :ref:`Required <autowiring-calls>`
+* :ref:`SubscribedService <service-subscribers-service-subscriber-trait>`
+
+Dependency Injection
+~~~~~~~~~~~~~~~~~~~~
+
+* :ref:`AsTaggedItem <tags_as-tagged-item>`
+* :ref:`Autoconfigure <lazy-services_configuration>`
+* :ref:`AutoconfigureTag <di-instanceof>`
+* :ref:`TaggedIterator <tags_reference-tagged-services>`
+* :ref:`TaggedLocator <service-subscribers-locators_defining-service-locator>`
+* :ref:`Target <autowiring-multiple-implementations-same-type>`
+* :ref:`When <service-container_limiting-to-env>`
+
+EventDispatcher
+~~~~~~~~~~~~~~~
+
+* :ref:`AsEventListener <event-dispatcher_event-listener-attributes>`
+
+HttpKernel
+~~~~~~~~~~
+
+* :doc:`AsController </controller/service>`
+
+Messenger
+~~~~~~~~~
+
+* :ref:`AsMessageHandler <messenger-handler>`
+
+Routing
+~~~~~~~
+
+* :doc:`Route </routing>`
+
+Security
+~~~~~~~~
+
+* :ref:`CurrentUser <security-json-login>`
+
+Serializer
+~~~~~~~~~~
+
+* :ref:`Context <serializer_serializer-context>`
+* :ref:`DiscriminatorMap <serializer_interfaces-and-abstract-classes>`
+* :ref:`Groups <component-serializer-attributes-groups-annotations>`
+* :ref:`Ignore <serializer_ignoring-attributes>`
+* :ref:`MaxDepth <serializer_handling-serialization-depth>`
+* :ref:`SerializedName <serializer_name-conversion>`
+
+Validator
+~~~~~~~~~
+
+Each validation constraint comes with a PHP attribute. See
+:doc:`/reference/constraints` for a full list of validation constraints.

reference/map.rst.inc

@@ -35,4 +35,5 @@ Others
 * :doc:`Configuring the Kernel </reference/configuration/kernel>`
 * :doc:`Twig Extensions (forms, filters, tags, etc) Reference </reference/twig_reference>`
 * :doc:`/reference/dic_tags`
+* :doc:`Symfony Attributes Overview </reference/attributes>`
 * :doc:`/reference/events`

serializer.rst

@@ -90,7 +90,7 @@ possible to set the priority of the tag in order to decide the matching order.
     ``DateTime`` or ``DateTimeImmutable`` classes to avoid excessive memory
     usage and exposing internal details.
 
-.. _serializer-context:
+.. _serializer_serializer-context:
 
 Serializer Context
 ------------------

serializer/custom_context_builders.rst

@@ -11,7 +11,7 @@ How to Create your Custom Context Builder
 The :doc:`Serializer Component </components/serializer>` uses Normalizers
 and Encoders to transform any data to any data-structure (e.g. JSON).
 That serialization process can be configured thanks to a
-:ref:`serialization context <serializer-context>`, which can be built thanks to
+:ref:`serialization context <serializer_serializer-context>`, which can be built thanks to
 :ref:`context builders <component-serializer-context-builders>`.
 
 Each built-in normalizer/encoder has its related context builder. However, you

service_container.rst

@@ -240,6 +240,8 @@ each time you ask for it.
     If you'd prefer to manually wire your service, that's totally possible: see
     :ref:`services-explicitly-configure-wire-services`.
 
+.. _service-container_limiting-to-env:
+
 Limiting Services to a specific Symfony Environment
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

service_container/autowiring.rst

@@ -392,6 +392,8 @@ dealing with the ``TransformerInterface``.
             // ...
         }
 
+.. _autowiring-multiple-implementations-same-type:
+
 Dealing with Multiple Implementations of the Same Type
 ------------------------------------------------------