-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
Closed
Description
| Q | A |
|---|---|
| Bug report? | no |
| Feature request? | yes |
| BC Break report? | no |
| RFC? | yes |
| Symfony version | 4.1 |
Recently did a project where, for API purpose, we created an exception listener to transform those into specialized json responses.
The funny part is we now effectively disabled exception logging; discovered on prod :-) Because our custom response set, the built-in exception listener no longer runs; thus no logging.
The trick is to copy Symfony\Component\HttpKernel\EventListener\ExceptionListener::logException() and call as needed. Basically you need to dive into internals to figure it out.
Wondering... can we move the logException() logic and make it a (better) feature?
jvasseur, Koc, mateuszsip, PabloKowalczyk, ovrflo and 3 more
Metadata
Metadata
Assignees
Labels
No labels