Conversation
|
|
||
| it('should include field name in case of attribute interpolation', () => { | ||
| const message = `Previous value for 'attr.id': 'Expressions: a and initial!'. Current value: 'Expressions: a and changed!'`; | ||
| const message = `Expression has changed after it was checked. Previous value: 'initial'. Current value: 'changed'`; |
There was a problem hiding this comment.
This changed, because the error comes from the interpolate instructions which don't know what attribute they're bound to.
There was a problem hiding this comment.
Right, this makes the error message less useful but I think it is the tradeoff we should make
|
|
||
| it('should include field name in case of attribute interpolation', () => { | ||
| const message = `Previous value for 'attr.id': 'Expressions: a and initial!'. Current value: 'Expressions: a and changed!'`; | ||
| const message = `Expression has changed after it was checked. Previous value: 'initial'. Current value: 'changed'`; |
There was a problem hiding this comment.
Right, this makes the error message less useful but I think it is the tradeoff we should make
Adds the new `interpolate*` instructions that can be passed into other instructions and used to replace our existing flavors of interpolations.
Replaces the attribute interpolation instructions with `attribute` plus the new `interpolateX` instruction. This allows to reduce our overall instruction footprint.
The attribute interpolation instructions aren't used anymore so we can remove them.
Updates the `bindingUpdated` function to handle `NO_CHANGE` instead of throwing. This will allow us to reuse instructions across more cases.
b717dd8 to
7ce1fd5
Compare
Adds the new `interpolate*` instructions that can be passed into other instructions and used to replace our existing flavors of interpolations. PR Close #61557
) Replaces the attribute interpolation instructions with `attribute` plus the new `interpolateX` instruction. This allows to reduce our overall instruction footprint. PR Close #61557
The attribute interpolation instructions aren't used anymore so we can remove them. PR Close #61557
Updates the `bindingUpdated` function to handle `NO_CHANGE` instead of throwing. This will allow us to reuse instructions across more cases. PR Close #61557
) Replaces the attribute interpolation instructions with `attribute` plus the new `interpolateX` instruction. This allows to reduce our overall instruction footprint. PR Close #61557
The attribute interpolation instructions aren't used anymore so we can remove them. PR Close #61557
Updates the `bindingUpdated` function to handle `NO_CHANGE` instead of throwing. This will allow us to reuse instructions across more cases. PR Close #61557
|
This PR was merged into the repository by commit 1650a85. The changes were merged into the following branches: main, 20.0.x |
|
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. |
Replaces the existing attribute interpolation instructions with a new format. For example previously we would generate
attributeInterpolate(name, ...)whereas now we generateattribute(name, interpolate(...)). This allows us to remove all of the specialized interpolation instructions.This initial PR only deals with attributes, but if there aren't any breakages, we can roll out the approach to all interpolations, saving us ~40 instructions from the set.