From 88408715d43bf8d3c16a7e17ef5a3812be078f54 Mon Sep 17 00:00:00 2001 From: Alexandre Daubois Date: Wed, 5 Jul 2023 18:16:24 +0200 Subject: [PATCH] [Messenger] Remove remaining deprecations --- messenger.rst | 12 ------------ messenger/multiple_buses.rst | 3 --- 2 files changed, 15 deletions(-) diff --git a/messenger.rst b/messenger.rst index 5a84e517415..95ae08a8ea8 100644 --- 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 index 49e4d3e568e..42ff8dc85d4 100644 --- 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