feat(core): Add provider which reports unhandled errors on window t…#60704
Closed
atscott wants to merge 1 commit intoangular:mainfrom
Closed
feat(core): Add provider which reports unhandled errors on window t…#60704atscott wants to merge 1 commit intoangular:mainfrom
atscott wants to merge 1 commit intoangular:mainfrom
Conversation
arturovt
reviewed
Apr 2, 2025
AndrewKushnir
approved these changes
Apr 4, 2025
Contributor
AndrewKushnir
left a comment
There was a problem hiding this comment.
Reviewed-for: public-api
devversion
approved these changes
Apr 4, 2025
Member
devversion
left a comment
There was a problem hiding this comment.
LGTM
Reviewed-for: public-api
8 tasks
b0e32ed to
0a17cdf
Compare
kirjs
approved these changes
Apr 7, 2025
Contributor
kirjs
left a comment
There was a problem hiding this comment.
LGTM
Reviewed-for: public-api
bf90b0a to
cfdf817
Compare
syamoka
approved these changes
Apr 8, 2025
0d690ec to
dfad3c3
Compare
DerZyklop
suggested changes
Apr 10, 2025
dfad3c3 to
84c3161
Compare
thePunderWoman
approved these changes
Apr 10, 2025
Contributor
thePunderWoman
left a comment
There was a problem hiding this comment.
reviewed-for: fw-general, public-api
DerZyklop
approved these changes
Apr 11, 2025
9c91b81 to
c6e8860
Compare
…ErrorHandler This commit adds a provider that installs listeners on the browser window to forward unhandled promise rejections and uncaught errors to the `ErrorHandler`. This is useful for both ZoneJS and Zoneless applications. For apps using ZoneJS, errors can reach the window when they happen outside the Angular Zone. For Zoneless apps, any errors not explicitly caught by the framework can reach the window. Without this provider, these errors would otherwise not be reported to `ErrorHandler`. We will/should consider adding this provider to apps by default in the cli. In addition, it should be mentioned in the (to be created) documentation page on error handling in Angular. relates to angular#56240
c6e8860 to
37ec7ed
Compare
Contributor
|
This PR was merged into the repository by commit 65adb30. The changes were merged into the following branches: main |
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…o ErrorHandler
This commit adds a provider that installs listeners on the browser window to forward unhandled promise rejections and uncaught errors to the
ErrorHandler. This is useful for both ZoneJS and Zoneless applications. For apps using ZoneJS, errors can reach the window when they happen outside the Angular Zone. For Zoneless apps, any errors not explicitly caught by the framework can reach the window. Without this provider, these errors would otherwise not be reported toErrorHandler.We will/should consider adding this provider to apps by default in the cli. In addition, it should be mentioned in the (to be created) documentation page on error handling in Angular.