Skip to content

Commit a582e1c

Browse files
committed
Incorporate further excellent feedback from @HeahDude
1 parent 0affc6b commit a582e1c

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

workflow/usage.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -605,15 +605,13 @@ In a Flash message in your Controller::
605605
$title = $workflow->getMetadataStore()->getMetadata('title', $transition);
606606
$this->addFlash('info', "You have successfully applied the transition with title: '$title'");
607607

608-
In a listener, access via the Event
609-
610608
Metadata can also be accessed in a Listener, from the Event object.
611609

612-
The example below uses a new feature introduced in 4.1 called Transition Blockers. These let you
610+
Using transition blockers you can
613611
return a user-friendly error message when you stop a transition from happening. In the example we
614-
get this user-friendly message from the Event's metadata, giving you an easy place to manage the
615-
text. This is a contrived example; in production systems you may prefer to use the
616-
:doc:`Translation </components/translation>` component to manage text::
612+
get this message from the :class:`Symfony\\Component\\Workflow\\Event\\Event`'s metadata, giving
613+
you an easy place to manage the text. This is a contrived example; in production code you may
614+
prefer to use the :doc:`Translation </components/translation>` component to manage messages::
617615

618616
namespace App\Listener\Workflow\Task;
619617

@@ -643,7 +641,9 @@ text. This is a contrived example; in production systems you may prefer to use t
643641
}
644642
}
645643

644+
.. versionadded:: 4.1
646645

646+
The transition blockers were added in version 4.1.
647647

648648
In Twig templates, metadata is available via the ``workflow_metadata()`` function:
649649

0 commit comments

Comments
 (0)