-
Notifications
You must be signed in to change notification settings - Fork 132
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
Wrong namespace of exception handler #38
Comments
Yeah, this is for sure an issue, and likely going to be incredibly difficult to fix. |
I was able to thwart this issue by doing the following:
|
Also having this issue. Should bugsnag extend Illuminate\Foundation\Exceptions\Handler instead? |
An alt to doing what adamgoose suggested. http://laravel.com/docs/5.0/errors#handling-errors We can temp put this in the main handler:
We need to override the singleton they bind in their service provider but keep all the rest of the functionality. So then make your own exception service provider and place it right after the bugsnag one with this in it:
|
I'd love feedback on #40 — would that work for everyone? |
The namespace of the exception handler class seems to be hardcoded. Due to the PSR4 autoloader in L5 its best practice to rename the namespace of the app directory (http://laravel.com/docs/5.0/configuration#after-installation).
Handler.php is correctly namespaced, but wrong referenced in BugsnagExceptionHandler.php
The text was updated successfully, but these errors were encountered: