fix(@angular/build): support per component updates of multi-component files #29538
Conversation
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
… files The HMR component update candidate analysis has been improved to now perform more fine-grained checks for cases where more than one component is present in a single TypeScript file. Previously it was possible for all components present in a TypeScript file to be considered update candidates when only one of the components had relevant changes to its template and/or styles.
clydin
added
the
action: review
alan-agius4
approved these changes
Feb 12, 2025
alan-agius4
added
action: merge
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The HMR component update candidate analysis has been improved to now perform more fine-grained checks for cases where more than one component is present in a single TypeScript file. Previously it was possible for all components present in a TypeScript file to be considered update candidates when only one of the components had relevant changes to its template and/or styles.