minor #11977 pushing autoconfigure note into code block (weaverryan)

javiereguiluz · javiereguiluz · commit 6a59686b7e35 · 2019-07-18T09:50:41.000+02:00
This PR was merged into the 4.3 branch. Discussion ---------- pushing autoconfigure note into code block The next example below already does this. Most people WILL need `autoconfigure: false`, so let's include it in the actual code. Commits ------- a526108 pushing autoconfigure into code block
diff --git a/messenger/multiple_buses.rst b/messenger/multiple_buses.rst
@@ -120,6 +120,9 @@ you can restrict each handler to a specific bus using the ``messenger.message_ha
         services:
             App\MessageHandler\SomeCommandHandler:
                 tags: [{ name: messenger.message_handler, bus: messenger.bus.commands }]
+                # prevent handlers from being registered twice (or you can remove
+                # the MessageHandlerInterface that autoconfigure uses to find handlers)
+                autoconfigure: false
 
     .. code-block:: xml
 
@@ -147,14 +150,6 @@ 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:`service autoconfiguration <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:
