Skip to content

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented May 6, 2025

Note: this is a patch port of #61137.

Fixes that the runtime was throwing a DI error when attempting to inject a missing useExisting provider, despite the call being optional.

The problem was that when the provider has useExisting, we do a second inject call under the hood which didn't include the inject flags from the original call.

Fixes #61121.

Fixes that the runtime was throwing a DI error when attempting to inject a missing `useExisting` provider, despite the call being optional.

The problem was that when the provider has `useExisting`, we do a second `inject` call under the hood which didn't include the inject flags from the original call.

Fixes angular#61121.
@crisbeto crisbeto requested a review from AndrewKushnir May 6, 2025 19:05
@crisbeto crisbeto added action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release labels May 6, 2025
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label May 6, 2025
@ngbot ngbot bot added this to the Backlog milestone May 6, 2025
@AndrewKushnir AndrewKushnir 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 and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels May 6, 2025
@AndrewKushnir
Copy link
Contributor

This PR was merged into the repository by commit 4623b61.

The changes were merged into the following branches: 19.2.x

AndrewKushnir pushed a commit that referenced this pull request May 6, 2025
…61152)

Fixes that the runtime was throwing a DI error when attempting to inject a missing `useExisting` provider, despite the call being optional.

The problem was that when the provider has `useExisting`, we do a second `inject` call under the hood which didn't include the inject flags from the original call.

Fixes #61121.

PR Close #61152
@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 Jun 6, 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: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants