Allow MapAttribute instances to be used as the RHS in expressions. #488
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The expression classes assume that whenever an attribute appears in the right hand side argument that the resulting expression should use the attribute's path. That allows users to compare two attributes of an item or to update one attribute of the item based on another. For example:
However, the code failed to consider that some attribute classes, specifically MapAttribute and its subclasses, can sometime act as AttributeContainer objects depending on the context. When instantiated as an attribute container, the instance should behave as a Value in the right hand side of an expression: