Merge branch '4.3' into 4.4

* 4.3:
  Fix example WhenUserRegisteredThenSendWelcomeEmail
  Remove double word
  Fix supervisor: need to use the group:* to start all processes in this group
  pushing autoconfigure into code block
  Update workflow.rst

Author: javiereguiluz

components/workflow.rst

@@ -32,28 +32,30 @@ a ``Definition`` and a way to write the states to the objects (i.e. an
 instance of a :class:`Symfony\\Component\\Workflow\\MarkingStore\\MarkingStoreInterface`).
 
 Consider the following example for a blog post. A post can have one of a number
-of predefined statuses (`draft`, `review`, `rejected`, `published`). In a workflow,
+of predefined statuses (`draft`, `reviewed`, `rejected`, `published`). In a workflow,
 these statuses are called **places**. You can define the workflow like this::
 
     use Symfony\Component\Workflow\DefinitionBuilder;
-    use Symfony\Component\Workflow\MarkingStore\SingleStateMarkingStore;
+    use Symfony\Component\Workflow\MarkingStore\MethodMarkingStore;
     use Symfony\Component\Workflow\Transition;
     use Symfony\Component\Workflow\Workflow;
 
     $definitionBuilder = new DefinitionBuilder();
-    $definition = $definitionBuilder->addPlaces(['draft', 'review', 'rejected', 'published'])
+    $definition = $definitionBuilder->addPlaces(['draft', 'reviewed', 'rejected', 'published'])
         // Transitions are defined with a unique name, an origin place and a destination place
-        ->addTransition(new Transition('to_review', 'draft', 'review'))
-        ->addTransition(new Transition('publish', 'review', 'published'))
-        ->addTransition(new Transition('reject', 'review', 'rejected'))
+        ->addTransition(new Transition('to_review', 'draft', 'reviewed'))
+        ->addTransition(new Transition('publish', 'reviewed', 'published'))
+        ->addTransition(new Transition('reject', 'reviewed', 'rejected'))
         ->build()
     ;
 
-    $marking = new SingleStateMarkingStore('currentState');
+    $singleState = true; // true if the subject can be in only one state at a given time
+    $property = 'currentState' // subject property name where the state is stored
+    $marking = new MethodMarkingStore($singleState, $property);
     $workflow = new Workflow($definition, $marking);
 
-The ``Workflow`` can now help you to decide what actions are allowed
-on a blog post depending on what *place* it is in. This will keep your domain
+The ``Workflow`` can now help you to decide what *transitions* (actions) are allowed
+on a blog post depending on what *place* (state) it is in. This will keep your domain
 logic in one place and not spread all over your application.
 
 When you define multiple workflows you should consider using a ``Registry``,
@@ -66,11 +68,11 @@ are trying to use it with::
     use Symfony\Component\Workflow\Registry;
     use Symfony\Component\Workflow\SupportStrategy\InstanceOfSupportStrategy;
 
-    $blogWorkflow = ...
+    $blogPostWorkflow = ...
     $newsletterWorkflow = ...
 
     $registry = new Registry();
-    $registry->addWorkflow($blogWorkflow, new InstanceOfSupportStrategy(BlogPost::class));
+    $registry->addWorkflow($blogPostWorkflow, new InstanceOfSupportStrategy(BlogPost::class));
     $registry->addWorkflow($newsletterWorkflow, new InstanceOfSupportStrategy(Newsletter::class));
 
 Usage
@@ -80,17 +82,17 @@ When you have configured a ``Registry`` with your workflows,
 you can retrieve a workflow from it and use it as follows::
 
     // ...
-    // Consider that $post is in state "draft" by default
-    $post = new BlogPost();
-    $workflow = $registry->get($post);
+    // Consider that $blogPost is in place "draft" by default
+    $blogPost = new BlogPost();
+    $workflow = $registry->get($blogPost);
 
-    $workflow->can($post, 'publish'); // False
-    $workflow->can($post, 'to_review'); // True
+    $workflow->can($blogPost, 'publish'); // False
+    $workflow->can($blogPost, 'to_review'); // True
 
-    $workflow->apply($post, 'to_review'); // $post is now in state "review"
+    $workflow->apply($blogPost, 'to_review'); // $blogPost is now in place "reviewed"
 
-    $workflow->can($post, 'publish'); // True
-    $workflow->getEnabledTransitions($post); // ['publish', 'reject']
+    $workflow->can($blogPost, 'publish'); // True
+    $workflow->getEnabledTransitions($blogPost); // $blogPost can perform transition "publish" or "reject"
 
 Learn more
 ----------

messenger.rst

@@ -7,7 +7,7 @@ Messenger: Sync & Queued Message Handling
 Messenger provides a message bus with the ability to send messages and then
 handle them immediately in your application or send them through transports
 (e.g. queues) to be handled later. To learn more deeply about it, read the
-:doc:`Messenger component docs </components/messenger>` docs.
+:doc:`Messenger component docs </components/messenger>`.
 
 Installation
 ------------
@@ -619,7 +619,7 @@ config and start your workers:
 
     $ sudo supervisorctl update
 
-    $ sudo supervisorctl start messenger-consume
+    $ sudo supervisorctl start messenger-consume:*
 
 See the `Supervisor docs`_ for more details.
 

messenger/message-recorder.rst

@@ -107,7 +107,7 @@ using the ``DispatchAfterCurrentBusMiddleware`` and adding a
 
         public function __invoke(UserRegistered $event)
         {
-            $user = $this->em->getRepository(User::class)->find(new User($event->getUuid()));
+            $user = $this->em->getRepository(User::class)->find($event->getUuid());
 
             $this->mailer->send(new RawMessage('Welcome '.$user->getFirstName()));
         }

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: