-
Notifications
You must be signed in to change notification settings - Fork 55
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
Implement better exception reporting. #39
Comments
Thanks to @jamesarnold for this suggestion. |
Done. Still need some templating, and a custom handler to report Application specific information. |
I mention here my idea: it would be awesome if the dev could have an own route for any exeption (not only the basic HTTP Exceptions) Generally something like `$handler->addException('MyException', 'route/to/handler/page'). It could generally make easier adding more basic exceptions to the core as well. |
Worth taking a look: |
@stevewest @WanWizard what do you think about switching to booboo? It has been moved to the league and seems to be more decent AND more importantly actively developed. |
If booboo is going to be better supported then I'd vote for switching to that. understand that @WanWizard has already integrated whoops and styled it so it's his call. |
It is not a problem, as I am working on the official import of the PrettyPageFormatter for booboo. So it won't be a big change. |
Implement http://filp.github.io/whoops/demo/ for nice informative error reporting.
The text was updated successfully, but these errors were encountered: