fix(ivy): reflect animations field directly into the output definition (#26322)
The 'animations' field of @Component metadata should be copied directly into the ngComponentDef for that component and should not pass through static resolution. Previously the animations array was statically resolved and then the values were translated back when generating ngComponentDef. PR Close #26322
This commit is contained in:

committed by
Jason Aden

parent
9623e7c639
commit
456f23f76a
@ -133,7 +133,7 @@ describe('compiler compliance: styling', () => {
|
||||
vars: 0,
|
||||
template: function MyComponent_Template(rf, $ctx$) {
|
||||
},
|
||||
animations: [{name: "foo123"}, {name: "trigger123"}]
|
||||
animations: [{name: 'foo123'}, {name: 'trigger123'}]
|
||||
});
|
||||
`;
|
||||
|
||||
|
Reference in New Issue
Block a user