From 7cb19e4eda993757264149bf506b2bf3064c69dd Mon Sep 17 00:00:00 2001 From: Fabien Potencier Date: Mon, 11 Sep 2017 11:28:36 -0700 Subject: [PATCH] added a note about profiler matcher deprecation --- profiler/matchers.rst | 5 +++++ reference/configuration/framework.rst | 4 ++++ 2 files changed, 9 insertions(+) diff --git a/profiler/matchers.rst b/profiler/matchers.rst index b974d6e9af3..f2b9c384ba8 100644 --- a/profiler/matchers.rst +++ b/profiler/matchers.rst @@ -4,6 +4,11 @@ How to Use Matchers to Enable the Profiler Conditionally ======================================================== +.. caution:: + + The possibility to use a matcher to enable the profiler conditionally is + deprecated since Symfony 3.4 and will be removed in 4.0. + The Symfony profiler is only activated in the development environment to not hurt your application performance. However, sometimes it may be useful to conditionally enable the profiler in the production environment to assist you in debugging diff --git a/reference/configuration/framework.rst b/reference/configuration/framework.rst index 50c5ac2cde0..f8b44a0c992 100644 --- a/reference/configuration/framework.rst +++ b/reference/configuration/framework.rst @@ -571,6 +571,10 @@ The DSN where to store the profiling information. matcher ....... +.. caution:: + + This option is deprecated since Symfony 3.4 and will be removed in 4.0. + Matcher options are configured to dynamically enable the profiler. For instance, based on the `ip`_ or :ref:`path `.