-
Notifications
You must be signed in to change notification settings - Fork 25.3k
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(ivy): provide an ability to match <ng-template> tags #27636
fix(ivy): provide an ability to match <ng-template> tags #27636
Conversation
52e51e4
to
b26bd1a
Compare
You can preview 3b74ade at https://pr27636-3b74ade.ngbuilds.io/. |
You can preview 7d7d158 at https://pr27636-7d7d158.ngbuilds.io/. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, just some nits
packages/compiler-cli/test/compliance/r3_view_compiler_directives_spec.ts
Outdated
Show resolved
Hide resolved
Prior to this change, we were unable to match directives using `ng-template` tags (for example the following selector would not work even though there might be some <ng-template>s in a template: `ng-template[directiveA]`. As a result, that broke some components that relies on such selectors to work. In order to resolve the problem, we now pass tag name to the `template` instruction (where we passed `null` before) and this tag name is used for matching at runtime. This update should also help support projecting containers, because the tag name is required to properly match such elements.
7d7d158
to
dcbf47a
Compare
You can preview dcbf47a at https://pr27636-dcbf47a.ngbuilds.io/. |
Thanks you for the review @kara! I've applied the necessary changes and will set this PR to "ready for merge" once all tests are completed. Thank you. |
You can preview d23e575 at https://pr27636-d23e575.ngbuilds.io/. |
Prior to this change, we were unable to match directives using `ng-template` tags (for example the following selector would not work even though there might be some <ng-template>s in a template: `ng-template[directiveA]`. As a result, that broke some components that relies on such selectors to work. In order to resolve the problem, we now pass tag name to the `template` instruction (where we passed `null` before) and this tag name is used for matching at runtime. This update should also help support projecting containers, because the tag name is required to properly match such elements. PR Close angular#27636
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. |
Prior to this change, we were unable to match directives using
ng-template
tags (for example the following selector would not work even though there might be some s in a template:ng-template[directiveA]
. As a result, that broke some components that relies on such selectors to work. In order to resolve the problem, we now pass tag name to thetemplate
instruction (where we passednull
before) and this tag name is used for matching at runtime. This update should also help support projecting containers, because the tag name is required to properly match such elements.Issue Number: FW-818.
Does this PR introduce a breaking change?