[8.x] Catch suppressed deprecation logs#40942
Conversation
|
I'm seeing a problem with this approach. Since it uses the Log facade, now it makes mocking that much less useful, since I have to expect various calls to it due to the framework trying to use the Log APIs. For example I get tests using Investigating this it has multiple calls failing and being catched. First one is actually this: from Not sure if I'm missing some basic way to fix the problem without having to rewrite a lot of tests. Any suggestions? |
|
For information, at present I found a workaround by overriding the symfony I'll try to file a but report or pull request for this as soon as I have a good idea on the best way to address it. |
|
@madpilot78 The #41057 pull request should address your issue. |
|
@nunomaduro It looks to be exactly what I was looking for, thanks! |
This pull requests closes #40854 by making Laravel's deprecation handler catch suppressed deprecations.
The motivation behind this pull request is the way Symfony manages deprecations, as they use the
@operator like so: