Skip to content
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

fix(core): use TNode instead of LView for mapping injector providers #52436

Conversation

AleksanderBodurri
Copy link
Member

@AleksanderBodurri AleksanderBodurri commented Oct 28, 2023

Previously, LViews were used here to be consistent with other debug APIs. Using LViews for tracking injector providers does not work because providers only get configured once per TNode type.

Now we use the TNode as the key to track element injector providers, allowing the injector for each item rendered in a list (ngFor or @for) to be targeted with debug APIs for inspecting providers

@AleksanderBodurri AleksanderBodurri changed the title getInjectorProvider Fixes getInjectorProviders Fixes Oct 28, 2023
@AleksanderBodurri AleksanderBodurri added target: patch This PR is targeted for the next patch release core: di labels Oct 28, 2023
@AndrewKushnir AndrewKushnir added this to the v17-final milestone Oct 30, 2023
@ngbot ngbot bot removed this from the v17-final milestone Oct 30, 2023
@AleksanderBodurri AleksanderBodurri changed the title getInjectorProviders Fixes getInjectorProviders Fix Oct 30, 2023
Previously, LViews were used here to be consistent with other debug APIs. Using LViews for tracking injector providers does not work because providers only get configured once per TNode type.

Now we use the TNode as the key to track element injector providers, allowing the injector for each item rendered in a list (`ngFor` or `@for`) to be targeted with debug APIs for inspecting providers
@AndrewKushnir AndrewKushnir changed the title getInjectorProviders Fix fix(core): use TNode instead of LView for mapping injector providers Oct 30, 2023
@AndrewKushnir AndrewKushnir added the action: presubmit The PR is in need of a google3 presubmit label Oct 30, 2023
@AndrewKushnir AndrewKushnir added this to the v17-final milestone Oct 30, 2023
@ngbot ngbot bot removed this from the v17-final milestone Oct 30, 2023
@AndrewKushnir
Copy link
Contributor

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 Oct 30, 2023
@atscott atscott added target: rc This PR is targeted for the next release-candidate and removed target: patch This PR is targeted for the next patch release labels Nov 3, 2023
@atscott
Copy link
Contributor

atscott commented Nov 3, 2023

@AleksanderBodurri updated target to rc since there was a conflict with patch. If this needs to be merged to 16.2.x as well, please open another PR to target that branch.

@atscott
Copy link
Contributor

atscott commented Nov 3, 2023

This PR was merged into the repository by commit 3d73b0c.

atscott pushed a commit that referenced this pull request Nov 3, 2023
…52436)

Previously, LViews were used here to be consistent with other debug APIs. Using LViews for tracking injector providers does not work because providers only get configured once per TNode type.

Now we use the TNode as the key to track element injector providers, allowing the injector for each item rendered in a list (`ngFor` or `@for`) to be targeted with debug APIs for inspecting providers

PR Close #52436
@atscott atscott closed this in 3d73b0c Nov 3, 2023
Abseil-byte pushed a commit to Abseil-byte/angular that referenced this pull request Nov 5, 2023
…ngular#52436)

Previously, LViews were used here to be consistent with other debug APIs. Using LViews for tracking injector providers does not work because providers only get configured once per TNode type.

Now we use the TNode as the key to track element injector providers, allowing the injector for each item rendered in a list (`ngFor` or `@for`) to be targeted with debug APIs for inspecting providers

PR Close angular#52436
@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 4, 2023
tbondwilkinson pushed a commit to tbondwilkinson/angular that referenced this pull request Dec 6, 2023
…ngular#52436)

Previously, LViews were used here to be consistent with other debug APIs. Using LViews for tracking injector providers does not work because providers only get configured once per TNode type.

Now we use the TNode as the key to track element injector providers, allowing the injector for each item rendered in a list (`ngFor` or `@for`) to be targeted with debug APIs for inspecting providers

PR Close angular#52436
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…ngular#52436)

Previously, LViews were used here to be consistent with other debug APIs. Using LViews for tracking injector providers does not work because providers only get configured once per TNode type.

Now we use the TNode as the key to track element injector providers, allowing the injector for each item rendered in a list (`ngFor` or `@for`) to be targeted with debug APIs for inspecting providers

PR Close angular#52436
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 core: di target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants