Skip to content

Add a note about profiler matcher deprecation #8388

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.

Sign up for GitHub

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
Sep 15, 2017
Merged

Add a note about profiler matcher deprecation #8388

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 5 additions & 0 deletions profiler/matchers.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 4 additions & 0 deletions reference/configuration/framework.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <reference-profiler-matcher-path>`.

Expand Down