Closed cweiske closed 10 months ago
That was not very Semver, sorry for that! Nevermind someone uses the class... We don't use it since a half decade.
How can we get exceptions into sentry on testing and staging systems, while at the same time see the full exception trace when an error occurs?
The ProductionExceptionHandler normally shows an EventId, which you can paste into the Issue search field in Sentry. Is that a way for you?
This is indeed a way, but it takes two more steps when debugging issues :(
Will keep the DebugExceptionHandler.
The README's changelog says:
(this came with 2e34725f89cf59a55e794e35adc655dd106e46ff, but no further explanation)
In #76 you remove the debugexceptionhandler class, but the commit also does not tell what the alternative is.
How can we get exceptions into sentry on testing and staging systems, while at the same time see the full exception trace when an error occurs?