Skip to content

[Messenger] Adds tip for handler misconfiguration #11699

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

[Messenger] Adds tip for handler misconfiguration #11699

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
67f3f76
Warn about multiple handlers.
Jun 7, 2019
f83e176
Fixes namespace for MessageHandlerInterface
Jun 8, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions messenger/multiple_buses.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,6 +197,14 @@ you can restrict each handler to a specific bus using the ``messenger.message_ha
This way, the ``App\MessageHandler\SomeCommandHandler`` handler will only be
known by the ``messenger.bus.commands`` bus.

.. tip::

If you manually restrict handlers be sure to have ``autoconfigure`` disabled,
or not implement the ``Symfony\Component\Messenger\Handler\MessageHandlerInterface``
as this might cause your handler to be registered twice.

See :ref:`autoconfigure <services-autoconfigure>` for more information.

You can also automatically add this tag to a number of classes by following
a naming convention and registering all of the handler services by name with
the correct tag:
Expand Down