From 2a78bb9cd6fb460396660b6c81d92f8a6c9d08b6 Mon Sep 17 00:00:00 2001 From: Christian Flothmann Date: Fri, 23 Feb 2018 17:02:15 +0100 Subject: [PATCH] remove old versionadded directives --- components/security/firewall.rst | 3 --- components/translation/usage.rst | 3 --- components/yaml.rst | 3 --- routing/custom_route_loader.rst | 3 --- service_container.rst | 3 --- validation/sequence_provider.rst | 4 ---- 6 files changed, 19 deletions(-) diff --git a/components/security/firewall.rst b/components/security/firewall.rst index 1f218c7cfc1..114c074c0e1 100644 --- a/components/security/firewall.rst +++ b/components/security/firewall.rst @@ -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. diff --git a/components/translation/usage.rst b/components/translation/usage.rst index f0dd83e1636..d3454ad055c 100644 --- a/components/translation/usage.rst +++ b/components/translation/usage.rst @@ -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 diff --git a/components/yaml.rst b/components/yaml.rst index 47650ec1ce0..c50d755f0c3 100644 --- a/components/yaml.rst +++ b/components/yaml.rst @@ -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:: diff --git a/routing/custom_route_loader.rst b/routing/custom_route_loader.rst index 5b50d887b26..64487e9259b 100644 --- a/routing/custom_route_loader.rst +++ b/routing/custom_route_loader.rst @@ -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. diff --git a/service_container.rst b/service_container.rst index 6bcd4ac94e4..99254eacefc 100644 --- a/service_container.rst +++ b/service_container.rst @@ -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: diff --git a/validation/sequence_provider.rst b/validation/sequence_provider.rst index 046ea2f414f..8d42ea29b5b 100644 --- a/validation/sequence_provider.rst +++ b/validation/sequence_provider.rst @@ -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: