-
Notifications
You must be signed in to change notification settings - Fork 25.9k
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
refactor(core): remove deprecated parameter for ErrorHandler
#18759
Conversation
packages/core/src/error_handler.ts
Outdated
* rethrow. | ||
*/ | ||
deprecatedParameter?: boolean) {} | ||
constructor() {} |
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.
remove the ctor altogether
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.
done
BREAKING CHANGE: `ErrorHandler` no longer takes a parameter as it was not used and deprecated since v4.
a49542d
to
06e2ea4
Compare
You can preview a49542d at https://pr18759-a49542d.ngbuilds.io/. |
You can preview 06e2ea4 at https://pr18759-06e2ea4.ngbuilds.io/. |
Parameter was used for whether to re-throw errors, see #15208 |
It was no longer used since v4, see the PR that you linked. |
Yes @ocombe, since 4.0.0-rc.4 ... went completely unnoticed to me ... It was also the only breaking change I had for migrating from v4 to v5! Cheers! 👍 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Type
What kind of change does this PR introduce?
What is the current behavior?
ErrorHandler
was taking a parameter but was not using it.What is the new behavior?
ErrorHandler
no longer takes a parameter as it was not used and deprecated since v4.Does this PR introduce a breaking change?