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.
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
Rework to use only listeners #204
Conversation
Note to self: is getsentry/sentry-php#788 is merged/tagged, it will break this one. We need to wait that before releasing a stable version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me 👍
@Jean85 if we want to strictly follow semver then that PR will be merged only in |
It would break in the fact that you will add a new handler, that I would have to remove to avoid double-reporting of fatal errors. |
While testing the beta1, I discovered that Sentry's error handler wasn't triggered, if not only on the most fatal errors. Any other intermediate approach lead to double-reporting of errors (like #156), so I have to fall back to using the framework events, and disable Sentry's error handler.