Skip to content

Commit c1c755e

Browse files
committed
Removed unneeded versionadded directives
1 parent d627a26 commit c1c755e

File tree

1 file changed

+0
-13
lines changed

1 file changed

+0
-13
lines changed

workflow.rst

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -197,10 +197,6 @@ As configured, the following property is used by the marking store::
197197
Setting the ``audit_trail.enabled`` option to ``true`` makes the application
198198
generate detailed log messages for the workflow activity.
199199

200-
.. versionadded:: 3.3
201-
202-
The ``audit_trail`` option was introduced in Symfony 3.3.
203-
204200
With this workflow named ``blog_publishing``, you can get help to decide
205201
what actions are allowed on a blog post::
206202

@@ -406,10 +402,6 @@ This means that each event has access to the following information:
406402
:method:`Symfony\\Component\\Workflow\\Event\\Event::getWorkflowName`
407403
Returns a string with the name of the workflow that triggered the event.
408404

409-
.. versionadded:: 3.3
410-
411-
The ``getWorkflowName()`` method was introduced in Symfony 3.3.
412-
413405
For Guard Events, there is an extended class :class:`Symfony\\Component\\Workflow\\Event\\GuardEvent`.
414406
This class has two more methods:
415407

@@ -475,11 +467,6 @@ of domain logic in your templates:
475467
``workflow_has_marked_place()``
476468
Returns ``true`` if the marking of the given object has the given state.
477469

478-
.. versionadded:: 3.3
479-
480-
The ``workflow_marked_places()`` and ``workflow_has_marked_place()``
481-
functions were introduced in Symfony 3.3.
482-
483470
The following example shows these functions in action:
484471

485472
.. code-block:: html+twig

0 commit comments

Comments
 (0)