Skip to content

fix(core): handle hydration of multiple nodes projected in a single slot#53270

Closed
AndrewKushnir wants to merge 1 commit intoangular:mainfrom
AndrewKushnir:hydration_projection_fix
Closed

fix(core): handle hydration of multiple nodes projected in a single slot#53270
AndrewKushnir wants to merge 1 commit intoangular:mainfrom
AndrewKushnir:hydration_projection_fix

Conversation

@AndrewKushnir
Copy link
Contributor

This commit updates the logic to handle hydration of multiple nodes projected in a single slot. Currently, in case component nodes are content-projected and their order is changed during the projection, hydration can not find the correct element. With this fix, extra annotation info would be included for such nodes and hydration logic at runtime will use it to locate the right element.

Resolves #53246.

PR Type

What kind of change does this PR introduce?

  • Bugfix

Does this PR introduce a breaking change?

  • Yes
  • No

@AndrewKushnir AndrewKushnir added action: review The PR is still awaiting reviews from at least one requested reviewer area: core Issues related to the framework runtime target: patch This PR is targeted for the next patch release core: hydration labels Nov 29, 2023
@ngbot ngbot bot modified the milestone: Backlog Nov 29, 2023
This commit updates the logic to handle hydration of multiple nodes projected in a single slot. Currently, in case component nodes are content-projected and their order is changed during the projection, hydration can not find the correct element. With this fix, extra annotation info would be included for such nodes and hydration logic at runtime will use it to locate the right element.

Resolves angular#53246.
@AndrewKushnir AndrewKushnir force-pushed the hydration_projection_fix branch from 9859c92 to 6737ecb Compare November 29, 2023 22:37
Copy link
Contributor

@jessicajaniuk jessicajaniuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Glad this is a fairly simple fix.

@AndrewKushnir AndrewKushnir added action: presubmit The PR is in need of a google3 presubmit and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Nov 29, 2023
@AndrewKushnir
Copy link
Contributor Author

Presubmit.

@AndrewKushnir AndrewKushnir added action: merge The PR is ready for merge by the caretaker and removed action: presubmit The PR is in need of a google3 presubmit labels Nov 30, 2023
@dylhunn
Copy link
Contributor

dylhunn commented Nov 30, 2023

This PR was merged into the repository by commit 899f6c4.

@dylhunn dylhunn closed this in 899f6c4 Nov 30, 2023
dylhunn pushed a commit that referenced this pull request Nov 30, 2023
…lot (#53270)

This commit updates the logic to handle hydration of multiple nodes projected in a single slot. Currently, in case component nodes are content-projected and their order is changed during the projection, hydration can not find the correct element. With this fix, extra annotation info would be included for such nodes and hydration logic at runtime will use it to locate the right element.

Resolves #53246.

PR Close #53270
@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 31, 2023
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…lot (angular#53270)

This commit updates the logic to handle hydration of multiple nodes projected in a single slot. Currently, in case component nodes are content-projected and their order is changed during the projection, hydration can not find the correct element. With this fix, extra annotation info would be included for such nodes and hydration logic at runtime will use it to locate the right element.

Resolves angular#53246.

PR Close angular#53270
rlmestre pushed a commit to rlmestre/angular that referenced this pull request Jan 26, 2024
…lot (angular#53270)

This commit updates the logic to handle hydration of multiple nodes projected in a single slot. Currently, in case component nodes are content-projected and their order is changed during the projection, hydration can not find the correct element. With this fix, extra annotation info would be included for such nodes and hydration logic at runtime will use it to locate the right element.

Resolves angular#53246.

PR Close angular#53270
amilamen pushed a commit to amilamen/angular that referenced this pull request Jan 26, 2024
…lot (angular#53270)

This commit updates the logic to handle hydration of multiple nodes projected in a single slot. Currently, in case component nodes are content-projected and their order is changed during the projection, hydration can not find the correct element. With this fix, extra annotation info would be included for such nodes and hydration logic at runtime will use it to locate the right element.

Resolves angular#53246.

PR Close angular#53270
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 core: hydration target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Hydration error when projecting multiple component nodes into different slots

3 participants

Comments