fix(ivy): setting up animation properties correctly (FW-643) (#27496)
Prior to this change, animation properties were defined as element attributes, which caused errors at runtime. Now all animation-related attributes are defined as element properties. Also as a part of this update, we start to account for bindings used in animations, which was previously missing. PR Close #27496
This commit is contained in:

committed by
Igor Minar

parent
4da739a970
commit
c71d7b5633
@ -307,10 +307,10 @@ export function compileComponentFromMetadata(
|
||||
definitionMap.set('encapsulation', o.literal(meta.encapsulation));
|
||||
}
|
||||
|
||||
// e.g. `animations: [trigger('123', [])]`
|
||||
// e.g. `animation: [trigger('123', [])]`
|
||||
if (meta.animations !== null) {
|
||||
definitionMap.set(
|
||||
'data', o.literalMap([{key: 'animations', value: meta.animations, quoted: false}]));
|
||||
'data', o.literalMap([{key: 'animation', value: meta.animations, quoted: false}]));
|
||||
}
|
||||
|
||||
// On the type side, remove newlines from the selector as it will need to fit into a TypeScript
|
||||
|
Reference in New Issue
Block a user