Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(core): defer block render failures should report to application e… #60149

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

Closed
wants to merge 1 commit into from

Conversation

atscott
Copy link
Contributor

@atscott atscott commented Feb 27, 2025

…rror handler

This commit updates error reporting of defer blocks to go to the application root error handler rather than the ErrorHandler token that may be provided by users. This ensures Angular has control over what happens when these errors are reported.

@atscott atscott added the target: major This PR is targeted for the next major release label Feb 27, 2025
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label Feb 27, 2025
@ngbot ngbot bot added this to the Backlog milestone Feb 27, 2025
@atscott atscott force-pushed the handleApplicationError branch 2 times, most recently from 0284276 to 3ee2d66 Compare February 28, 2025 21:19
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label Feb 28, 2025
@mmalerba
Copy link
Contributor

mmalerba commented Mar 3, 2025

@atscott looks like there's a failing test

@mmalerba mmalerba removed the action: merge The PR is ready for merge by the caretaker label Mar 3, 2025
…rror handler

This commit updates error reporting of defer blocks to go to the
application root error handler rather than the `ErrorHandler` token that
may be provided by users. This ensures Angular has control over what
happens when these errors are reported.
@atscott atscott force-pushed the handleApplicationError branch from 3ee2d66 to 5043217 Compare March 3, 2025 18:27
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label Mar 3, 2025
@mmalerba
Copy link
Contributor

mmalerba commented Mar 4, 2025

@atscott can you start the presubmit for this?

@mmalerba mmalerba removed the action: merge The PR is ready for merge by the caretaker label Mar 4, 2025
@atscott atscott added action: merge The PR is ready for merge by the caretaker merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note labels Mar 4, 2025
@atscott
Copy link
Contributor Author

atscott commented Mar 4, 2025

merge assistance: rerun green after the unrelated failures from this morning

@mmalerba
Copy link
Contributor

mmalerba commented Mar 4, 2025

This PR was merged into the repository by commit fd12220.

The changes were merged into the following branches: main

@mmalerba mmalerba closed this in fd12220 Mar 4, 2025
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 4, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants