From de2802d71a35e3ba1dfd584e55a2ce42cc9442ab Mon Sep 17 00:00:00 2001 From: Christian Flothmann Date: Fri, 18 Jan 2019 11:34:04 +0100 Subject: [PATCH] remove Symfony 2/3 versionadded directives --- components/process.rst | 5 ----- components/serializer.rst | 5 ----- components/validator.rst | 4 ---- configuration/external_parameters.rst | 4 ---- console/request_context.rst | 4 ---- reference/configuration/framework.rst | 4 ---- reference/forms/types/number.rst | 5 ----- service_container/alias_private.rst | 4 ---- service_container/service_subscribers_locators.rst | 4 ---- testing.rst | 4 ---- 10 files changed, 43 deletions(-) diff --git a/components/process.rst b/components/process.rst index a1922a91ed0..9674e1af96a 100644 --- a/components/process.rst +++ b/components/process.rst @@ -112,11 +112,6 @@ with a non-zero code):: .. tip:: - .. versionadded:: 3.3 - - The ability to define commands as arrays of arguments was introduced in - Symfony 3.3. - Using array of arguments is the recommended way to define commands. This saves you from any escaping and allows sending signals seamlessly (e.g. to stop processes before completion.):: diff --git a/components/serializer.rst b/components/serializer.rst index 229209a06de..ae447f7c627 100644 --- a/components/serializer.rst +++ b/components/serializer.rst @@ -166,11 +166,6 @@ needs three parameters: #. The name of the class this information will be decoded to #. The encoder used to convert that information into an array -.. versionadded:: 3.3 - - Support for the ``allow_extra_attributes`` key in the context was introduced - in Symfony 3.3. - By default, additional attributes that are not mapped to the denormalized object will be ignored by the Serializer component. If you prefer to throw an exception when this happens, set the ``allow_extra_attributes`` context option to diff --git a/components/validator.rst b/components/validator.rst index f0c4edde217..77b531fc5f8 100644 --- a/components/validator.rst +++ b/components/validator.rst @@ -64,10 +64,6 @@ If you have lots of validation errors, you can filter them by error code:: // handle this specific error (display some message, send an email, etc.) } -.. versionadded:: 3.3 - - The ``findByCodes()`` method was introduced in Symfony 3.3. - Retrieving a Validator Instance ------------------------------- diff --git a/configuration/external_parameters.rst b/configuration/external_parameters.rst index bc114a8bcd2..362f1e1b302 100644 --- a/configuration/external_parameters.rst +++ b/configuration/external_parameters.rst @@ -137,10 +137,6 @@ the following: Environment Variable Processors ------------------------------- -.. versionadded:: 3.4 - - Environment variable processors were introduced in Symfony 3.4. - The values of environment variables are considered strings by default. However, your code may expect other data types, like integers or booleans. Symfony solves this problem with *processors*, which modify the contents of the diff --git a/console/request_context.rst b/console/request_context.rst index 4d8ff892f42..b8ffb907c6b 100644 --- a/console/request_context.rst +++ b/console/request_context.rst @@ -65,10 +65,6 @@ will override the defaults. $container->setParameter('asset.request_context.base_path', $container->getParameter('router.request_context.base_url')); $container->setParameter('asset.request_context.secure', true); -.. versionadded:: 3.4 - - The ``asset.request_context.*`` parameters were introduced in Symfony 3.4. - Configuring the Request Context per Command ------------------------------------------- diff --git a/reference/configuration/framework.rst b/reference/configuration/framework.rst index 242b45d9711..52d7e8c5867 100644 --- a/reference/configuration/framework.rst +++ b/reference/configuration/framework.rst @@ -1591,10 +1591,6 @@ for translation files. default_path ............ -.. versionadded:: 3.4 - - The ``default_path`` option was introduced in Symfony 3.4. - **type**: ``string`` **default**: ``%kernel.project_dir%/translations`` This option allows to define the path where the application translations files diff --git a/reference/forms/types/number.rst b/reference/forms/types/number.rst index e02efb84898..5f6a4c19200 100644 --- a/reference/forms/types/number.rst +++ b/reference/forms/types/number.rst @@ -45,11 +45,6 @@ Field Options scale ~~~~~ -.. versionadded:: 2.7 - - The ``scale`` option was introduced in Symfony 2.7. Prior to Symfony 2.7, - it was known as ``precision``. - **type**: ``integer`` **default**: Locale-specific (usually around ``3``) This specifies how many decimals will be allowed until the field rounds diff --git a/service_container/alias_private.rst b/service_container/alias_private.rst index 8762473bbf7..756ab691b68 100644 --- a/service_container/alias_private.rst +++ b/service_container/alias_private.rst @@ -153,10 +153,6 @@ Anonymous Services Anonymous services are only supported by the XML and YAML configuration formats. -.. versionadded:: 3.3 - - The feature to configure anonymous services in YAML was introduced in Symfony 3.3. - In some cases, you may want to prevent a service being used as a dependency of other services. This can be achieved by creating an anonymous service. These services are like regular services but they don't define an ID and they are diff --git a/service_container/service_subscribers_locators.rst b/service_container/service_subscribers_locators.rst index 1335f4d43ec..0e57547e9a9 100644 --- a/service_container/service_subscribers_locators.rst +++ b/service_container/service_subscribers_locators.rst @@ -4,10 +4,6 @@ Service Subscribers & Locators ============================== -.. versionadded:: 3.3 - - Service subscribers and locators were introduced in Symfony 3.3. - Sometimes, a service needs access to several other services without being sure that all of them will actually be used. In those cases, you may want the instantiation of the services to be lazy. However, that's not possible using diff --git a/testing.rst b/testing.rst index 0dbd036dc0a..fc147be942a 100644 --- a/testing.rst +++ b/testing.rst @@ -603,10 +603,6 @@ will no longer be followed:: Reporting Exceptions ~~~~~~~~~~~~~~~~~~~~ -.. versionadded:: 3.4 - - The ``catchExceptions()`` method was introduced in Symfony 3.4. - Debugging exceptions in functional tests may be difficult because by default they are caught and you need to look at the logs to see which exception was thrown. Disabling catching of exceptions in the test client allows the exception