-
Notifications
You must be signed in to change notification settings - Fork 27k
fix(core): control not recognized when input has directive injecting ViewContainerRef #64368
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
Conversation
2a55814 to
bd84966
Compare
bd84966 to
cc4fc57
Compare
|
(rebased to solve the conflict) |
cc4fc57 to
45aa8bb
Compare
|
It looks like the |
45aa8bb to
9fdf50c
Compare
5f60bfa to
e339787
Compare
e25de25 to
4eb01eb
Compare
4eb01eb to
810125d
Compare
…ViewContainerRef When a directive injects a `ViewContainerRef`, the runtime inserts a container that was throwing off the logic that recognizes native controls. These changes switch to check if the node is a native control through the `TNode`. This also makes it a bit less prone to breaking during SSR. Fixes angular#64362.
810125d to
a684c16
Compare
|
Rebased and added an early exit for the loop that checks the |
|
This PR was merged into the repository. The changes were merged into the following branches:
|
|
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. |


When a directive injects a
ViewContainerRef, the runtime inserts a container that was throwing off the logic that recognizes native controls.These changes switch to check if the node is a native control through the
TNode. This also makes it a bit less prone to breaking during SSR.Fixes #64362.