minor #18520 [Messenger] Remove remaining deprecations (alexandre-daubois)

javiereguiluz · javiereguiluz · commit a3242e2359ae · 2023-07-06T10:13:34.000+02:00
This PR was merged into the 7.0 branch. Discussion ---------- [Messenger] Remove remaining deprecations Part of #18507 (comment) Some Messenger removed deprecations doesn't appear in the doc (like `StopWorkerOnSigtermSignalListener `). So this should take care of what's remaining for this component 🙂 Commits ------- 8840871 [Messenger] Remove remaining deprecations
diff --git a/messenger.rst b/messenger.rst
@@ -1718,12 +1718,6 @@ during a request::
         }
     }
 
-.. versionadded:: 6.3
-
-    The namespace of the ``InMemoryTransport`` class changed in Symfony 6.3 from
-    ``Symfony\Component\Messenger\Transport\InMemoryTransport`` to
-    ``Symfony\Component\Messenger\Transport\InMemory\InMemoryTransport``.
-
 The transport has a number of options:
 
 ``serialize`` (boolean, default: ``false``)
@@ -2020,12 +2014,6 @@ A single handler class can handle multiple messages. For that add the
         }
     }
 
-.. deprecated:: 6.2
-
-    Implementing the :class:`Symfony\\Component\\Messenger\\Handler\\MessageSubscriberInterface`
-    is another way to handle multiple messages with one handler class. This
-    interface was deprecated in Symfony 6.2.
-
 Binding Handlers to Different Transports
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
diff --git a/messenger/multiple_buses.rst b/messenger/multiple_buses.rst
@@ -133,9 +133,6 @@ you can restrict each handler to a specific bus using the ``messenger.message_ha
         services:
             App\MessageHandler\SomeCommandHandler:
                 tags: [{ name: messenger.message_handler, bus: command.bus }]
-                # prevent handlers from being registered twice (or you can remove
-                # the MessageHandlerInterface that autoconfigure uses to find handlers)
-                autoconfigure: false
 
     .. code-block:: xml
 

Original file line number	Diff line number	Diff line change
`@@ -1718,12 +1718,6 @@ during a request::`
`1718`	`1718`	`}`
`1719`	`1719`	`}`
`1720`	`1720`
`1721`		`-.. versionadded:: 6.3`
`1722`		`-`
`1723`		- The namespace of the ``InMemoryTransport`` class changed in Symfony 6.3 from
`1724`		- ``Symfony\Component\Messenger\Transport\InMemoryTransport`` to
`1725`		- ``Symfony\Component\Messenger\Transport\InMemory\InMemoryTransport``.
`1726`		`-`
`1727`	`1721`	`The transport has a number of options:`
`1728`	`1722`
`1729`	`1723`	``serialize`` (boolean, default: ``false``)
`@@ -2020,12 +2014,6 @@ A single handler class can handle multiple messages. For that add the`
`2020`	`2014`	`}`
`2021`	`2015`	`}`
`2022`	`2016`
`2023`		`-.. deprecated:: 6.2`
`2024`		`-`
`2025`		- Implementing the :class:`Symfony\\Component\\Messenger\\Handler\\MessageSubscriberInterface`
`2026`		`- is another way to handle multiple messages with one handler class. This`
`2027`		`- interface was deprecated in Symfony 6.2.`
`2028`		`-`
`2029`	`2017`	`Binding Handlers to Different Transports`
`2030`	`2018`	`~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
`2031`	`2019`