8000 Remove old versionadded directives · symfony/symfony-docs@9774ef2 · GitHub
[go: up one dir, main page]
Skip to content

Commit 9774ef2

Browse files
OskarStarkOskarStark
committed
Remove old versionadded directives
1 parent ca90035 commit 9774ef2

File tree

5 files changed

+2
-31
lines changed

5 files changed

+2
-31
lines changed

‎components/expression_language/syntax.rst

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,6 @@ The component supports:
2121
* **null** - ``null``
2222
* **exponential** - also known as scientific (e.g. ``1.99E+3`` or ``1e-2``)
2323

24-
.. versionadded:: 4.4
25-
26-
The ``exponential`` literal was introduced in Symfony 4.4.
27-
2824
.. caution::
2925

3026
A backslash (``\``) must be escaped by 4 backslashes (``\\\\``) in a string

‎components/http_kernel.rst

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -530,18 +530,6 @@ object, which you can use to access the original exception via the
530530
method. A typical listener on this event will check for a certain type of
531531
exception and create an appropriate error ``Response``.
532532

533-
.. versionadded:: 4.4
534-
535-
The :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::getThrowable` and
536-
:method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::setThrowable` methods
537-
were introduced in Symfony 4.4.
538-
539-
.. deprecated:: 4.4
540-
541-
The :method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::getException` and
542-
:method:`Symfony\\Component\\HttpKernel\\Event\\ExceptionEvent::setException` methods
543-
are deprecated since Symfony 4.4.
544-
545533
For example, to generate a 404 page, you might throw a special type of exception
546534
and then add a listener on this event that looks for this exception and
547535
creates and returns a 404 ``Response``. In fact, the HttpKernel component

‎security/password_migration.rst

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,6 @@
44
How to Migrate a Password Hash
55
==============================
66

7-
.. versionadded:: 4.4
8-
9-
Password migration was introduced in Symfony 4.4.
10-
117
In order to protect passwords, it is recommended to store them using the latest
128
hash algorithms. This means that if a better hash algorithm is supported on the
139
system, the user's password should be rehashed and stored. Symfony provides this
@@ -122,8 +118,8 @@ is available to hash the user's password. If it is, it'll hash the correct
122118
password using the new hash. You can enable this behavior by implementing how
123119
this newly hashed password should be stored:
124120

125-
* `When using Doctrine's entity user provider <Upgrade the Password when using Doctrine>`_
126-
* `When using a custom user provider <Upgrade the Password when using a custom User Provider>`_
121+
* `When using Doctrine's entity user provider <Upgrade the Password when using Doctrine>`_
122+
* `When using a custom user provider <Upgrade the Password when using a custom User Provider>`_
127123

128124
After this, you're done and passwords are always hashed as secure as possible!
129125

‎service_container.rst

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -739,10 +739,6 @@ You can also use the ``bind`` keyword to bind specific arguments by name or type
739739
// ...
740740
};
741741
742-
.. versionadded:: 4.4
743-
744-
The feature to bind tagged services was introduced in Symfony 4.4.
745-
746742
By putting the ``bind`` key under ``_defaults``, you can specify the value of *any*
747743
argument for *any* service defined in this file! You can bind arguments by name
748744
(e.g. ``$adminEmail``), by type (e.g. ``Psr\Log\LoggerInterface``) or both

‎workflow.rst

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -339,11 +339,6 @@ order:
339339
The leaving and entering events are triggered even for transitions that stay
340340
in same place.
341341

342-
.. versionadded:: 4.3
343-
344-
Following events are also dispatched when the subject enters the workflow
345-
for the first time: ``workflow.entered`` and ``workflow.[worflow name].entered``.
346-
347342
Here is an example of how to enable logging for every time a "blog_publishing"
348343
workflow leaves a place::
349344

0 commit comments

Comments
 (0)
0