Skip to content

Conversation

clydin
Copy link
Member

@clydin clydin commented Nov 5, 2024

Now that additional result object types can be returned from the build system, the error overlay must be cleared on all non-error results. The introduction of component update results and eventual incremental results will now properly clear the error overlay after a successful build.

…or result

Now that additional result object types can be returned from the build
system, the error overlay must be cleared on all non-error results. The
introduction of component update results and eventual incremental results
will now properly clear the error overlay after a successful build.
@clydin clydin added the target: rc This PR is targeted for the next release-candidate label Nov 5, 2024
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Nov 5, 2024
@alan-agius4 alan-agius4 merged commit 99192a7 into angular:main Nov 5, 2024
33 of 34 checks passed
@alan-agius4
Copy link
Collaborator

The changes were merged into the following branches: main, 19.0.x

@clydin clydin deleted the dev-server/clear-error-overlay branch November 5, 2024 15:04
@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 Dec 6, 2024
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: @angular/build target: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants