8000 remove old versionadded directives by xabbuh · Pull Request #9325 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

remove old versionadded directives #9325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 23, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions components/security/firewall.rst
Original file line number Diff line number Diff line change
Expand Up @@ -91,9 +91,6 @@ further than allowed.
Firewall Config
~~~~~~~~~~~~~~~

.. versionadded:: 3.2
The ``FirewallConfig`` class was introduced in Symfony 3.2.

The information about a given firewall, such as its name, provider, context,
entry point and access denied URL, is provided by instances of the
:class:`Symfony\\Bundle\\SecurityBundle\\Security\\FirewallConfig` class.
Expand Down
3 changes: 0 additions & 3 deletions components/translation/usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -421,9 +421,6 @@ The ``$messages`` variable will have the following structure::
Adding Notes to Translation Contents
------------------------------------

.. versionadded: 3.4
The feature to load and dump translation notes was introduced in Symfony 3.4.

Sometimes translators need additional context to better decide how to translate
some content. This context can be provided with notes, which are a collection of
comments used to store end user readable information. The only format that
Expand Down
3 changes: 0 additions & 3 deletions components/yaml.rst
Original file line number Diff line number Diff line change
Expand Up @@ -367,9 +367,6 @@ Binary data is automatically parsed if they include the ``!!binary`` YAML tag
Parsing and Dumping Custom Tags
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. versionadded:: 3.3
Support for parsing and dumping custom tags was introduced in Symfony 3.3.

In addition to the built-in support of tags like ``!php/const`` and
``!!binary``, you can define your own custom YAML tags and parse them with the
``PARSE_CUSTOM_TAGS`` flag::
Expand Down
3 changes: 0 additions & 3 deletions routing/custom_route_loader.rst
Original file line number Diff line number Diff line change
Expand Up @@ -62,9 +62,6 @@ containing :class:`Symfony\\Component\\Routing\\Route` objects.
Loading Routes with a Custom Service
------------------------------------

.. versionadded:: 2.8
The option to load routes using Symfony services was introduced in Symfony 2.8.

Using a regular Symfony service is the simplest way to load routes in a
customized way. It's much easier than creating a full custom route loader, so
you should always consider this option first.
Expand Down
3 changes: 0 additions & 3 deletions service_container.rst
Original file line number Diff line number Diff line change
Expand Up @@ -866,9 +866,6 @@ them will not cause the container to be rebuilt.
Multiple Service Definitions Using the Same Namespace
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

.. versionadded:: 3.4
The ``namespace`` option in the YAML configuration was introduced in Symfony 3.4.

If you define services using the YAML config format, the PHP namespace is used
as the key of each configuration, so you can't define different service configs
for classes under the same namespace:
Expand Down
4 changes: 0 additions & 4 deletions validation/sequence_provider.rst
Original file line number Diff line number Diff line change
Expand Up @@ -288,10 +288,6 @@ method, which should return an array of groups to use::
}
}

.. versionadded:: 3.2
The feature to return a nested array to get violations from all groups was
introduced in Symfony 3.2.

At last, you have to notify the Validator component that your ``User`` class
provides a sequence of groups to be validated:

Expand Down
0