diff --git a/components/browser_kit.rst b/components/browser_kit.rst index a2afe27c0bc..bfaad93d4f9 100644 --- a/components/browser_kit.rst +++ b/components/browser_kit.rst @@ -8,13 +8,6 @@ The BrowserKit Component The BrowserKit component simulates the behavior of a web browser, allowing you to make requests, click on links and submit forms programmatically. -.. note:: - - In Symfony versions prior to 4.3, the BrowserKit component could only make - internal requests to your application. Starting from Symfony 4.3, this - component can also :ref:`make HTTP requests to any public site ` - when using it in combination with the :doc:`HttpClient component `. - Installation ------------ diff --git a/components/config/definition.rst b/components/config/definition.rst index 8ad8ae1b0c9..29d0715e722 100644 --- a/components/config/definition.rst +++ b/components/config/definition.rst @@ -780,7 +780,7 @@ the following ways: - ``ifTrue()`` - ``ifString()`` - ``ifNull()`` -- ``ifEmpty()`` (since Symfony 3.2) +- ``ifEmpty()`` - ``ifArray()`` - ``ifInArray()`` - ``ifNotInArray()`` diff --git a/components/event_dispatcher/container_aware_dispatcher.rst b/components/event_dispatcher/container_aware_dispatcher.rst deleted file mode 100644 index 659a94cee7a..00000000000 --- a/components/event_dispatcher/container_aware_dispatcher.rst +++ /dev/null @@ -1,10 +0,0 @@ -.. index:: - single: EventDispatcher; Service container aware - -The Container Aware Event Dispatcher -==================================== - -.. caution:: - - The ``ContainerAwareEventDispatcher`` was removed in Symfony 4.0. Use - ``EventDispatcher`` with closure-proxy injection instead. diff --git a/components/filesystem/lock_handler.rst b/components/filesystem/lock_handler.rst deleted file mode 100644 index 5997fd3887b..00000000000 --- a/components/filesystem/lock_handler.rst +++ /dev/null @@ -1,7 +0,0 @@ -LockHandler -=========== - -.. caution:: - - The ``LockHandler`` utility was removed in Symfony 4.0. Use the new Symfony - :doc:`Lock component ` instead. diff --git a/contributing/code/bc.rst b/contributing/code/bc.rst index 3f1e6164087..4c5eb1d4ca2 100644 --- a/contributing/code/bc.rst +++ b/contributing/code/bc.rst @@ -12,11 +12,6 @@ that release branch (5.x in the previous example). We also provide deprecation message triggered in the code base to help you with the migration process across major releases. -.. caution:: - - This promise was introduced with Symfony 2.3 and does not apply to previous - versions of Symfony. - However, backward compatibility comes in many different flavors. In fact, almost every change that we make to the framework can potentially break an application. For example, if we add a new method to a class, this will break an application diff --git a/profiler.rst b/profiler.rst index 49e804f45b2..42e925b89c8 100644 --- a/profiler.rst +++ b/profiler.rst @@ -110,16 +110,12 @@ need to create a custom data collector. Instead, use the built-in utilities to Consider using a professional profiler such as `Blackfire`_ to measure and analyze the execution of your application in detail. -Enabling the Profiler Conditionally ------------------------------------ +.. _enabling-the-profiler-conditionally: -.. caution:: - - The possibility to use a matcher to enable the profiler conditionally was - removed in Symfony 4.0. +Enabling the Profiler Programmatically +-------------------------------------- -Symfony Profiler cannot be enabled/disabled conditionally using matchers, because -that feature was removed in Symfony 4.0. However, you can use the ``enable()`` +Symfony Profiler can be enabled and disabled programmatically. You can use the ``enable()`` and ``disable()`` methods of the :class:`Symfony\\Component\\HttpKernel\\Profiler\\Profiler` class in your controllers to manage the profiler programmatically:: diff --git a/service_container.rst b/service_container.rst index d1ceb094333..f2be38267d6 100644 --- a/service_container.rst +++ b/service_container.rst @@ -1074,11 +1074,8 @@ unique string as the key of each service config: Explicitly Configuring Services and Arguments --------------------------------------------- -Prior to Symfony 3.3, all services and (typically) arguments were explicitly configured: -it was not possible to :ref:`load services automatically ` -and :ref:`autowiring ` was much less common. - -Both of these features are optional. And even if you use them, there may be some +:ref:`Loading services automatically ` +and :ref:`autowiring ` are optional. And even if you use them, there may be some cases where you want to manually wire a service. For example, suppose that you want to register *2* services for the ``SiteUpdateManager`` class - each with a different admin email. In this case, each needs to have a unique service id: