Change Evaluation function used for expanding json #4659
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related Issue
Fixes #4574
But opens #4646
Description
Changes the use of the evaluation function to remove the enclosing braces and add an equals sign "=" to evaluate the actions based on the guidance of the AEL team. For example, "${sort(createArray(2,1))}" is converted into "=sort(createArray(2,1))"
How Verified
The fix was verified adding an unit test that contains the same payload that originated the issue. If the json expansion were to fail it would throw an exception
Microsoft Reviewers: Open in CodeFlow