Closed
Description
Q | A |
---|---|
Bug report? | no |
Feature request? | no |
BC Break report? | no |
RFC? | yes |
Symfony version | 3.4 |
As commented by Fabien, we could deprecate the profiler.matcher
option:
The matcher configuration was added at a time where we thought that having the profiler in production could make sense (and so being able to enable it conditionally made sense). That's not the case anymore. Nobody should ever enable it in production.
With that in mind, I would go in the other direction and remove the matcher config altogether for Symfony 4.0 (deprecating it in 3.4 first of course).