-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
feat(ErrorHandler): use the angular ErrorHandler for reporting errors #667
Conversation
The ErrorHandler reports to the console by default, so it wouldn't be a breaking change. |
It is a breaking change if #635 gets released in v4. Shall I remove the breaking change from the commit message though? |
@jbedard The breaking change should remain, but the format should be altered so it shows in the changelog correctly..
|
@jbedard this one is ready to land once the commit message is updated. |
9eb1402
to
66973d1
Compare
Fixes ngrx#626 BREAKING CHANGE: the ErrorReporter has been replaced with ErrorHandler from angular/core. BEFORE: Errors were reported to the ngrx/effects ErrorReporter. The ErrorReporter would log to the console by default. AFTER: Errors are now reported to the @angular/core ErrorHandler.
66973d1
to
23b98b8
Compare
I've updated the commit message, and rebased. Let me know if the commit message is ok... |
LGTM |
Fixes #626
This is a v5 alternative to #635. Can potentially try to keep
InvalidActionError
andEffectError
but I'm not sure if that is a standard thing to do withErrorHandler
?BREAKING CHANGE:
Errors are now reported to the @angular/core ErrorHandler.
Errors are no longer reported to the console.