Repository navigation
Conversation
e44228d to
28ac0ee
Compare
ab41f11 to
5936f83
Compare
40b0416 to
a45b5fd
Compare
a45b5fd to
cb2b479
Compare
Those are never applied and we should throw at compiler time.
cb2b479 to
5fe7be1
Compare
mattrbeck
left a comment
There was a problem hiding this comment.
Does the partial linker re-parse templates? I wonder if adding this change without an exemption in the partial linker will cause breakages when parsing dependencies which still bind the class on ng-container
| @@ -242,6 +242,11 @@ class HtmlAstToIvyAst implements html.Visitor { | |||
| `Attribute bindings are not supported on ng-container. Use property bindings instead.`, | |||
There was a problem hiding this comment.
If a user wrote [attr.class]="foo" today, they'd get an error telling them to use [class]="foo", which would now also error. Maybe we can report these errors in a way that's a little more clear?
| ); | ||
| } else if ( | ||
| bound.type === BindingType.Class || | ||
| (bound.type === BindingType.Property && bound.name === 'class') |
There was a problem hiding this comment.
Would this be breaking if a directive has a "class" input today?
| ); | ||
| } else if ( | ||
| bound.type === BindingType.Class || | ||
| (bound.type === BindingType.Property && bound.name === 'class') |
There was a problem hiding this comment.
Should we also check if bound.name === 'style'?
This is the same change as angular#70808 but for g3 only due to its breaking nature.
|
This is one case of #71881. #71882 reports class bindings on If both land, class bindings get the parse error and NG8031, so this needs reconciliation with #71882 and #71884 before merge. |
This is the same change as #70808 but for g3 only due to its breaking nature.
Those are never applied and we should throw at compiler time.
class attributes are still supported because we allow them for content projection purposes.