flogo expressions support for rule conditions #71
Conversation
This file contains hidden or 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
Merge branch 'expr' into noschema
fm-tibco
approved these changes
Nov 11, 2019
Contributor
|
This PR can be ignored as the same content is available in other PR #97 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Support flogo expressions syntax for rule condition evaluation such as:
$.t2.p2 > $.t1.p1wheret2andt1are tuple types andp2andp1are their respective properties(See
ruleapi/tests/expr_*tests for usage)Additionally, when run as a flogo actiontype, support for environment variables and flogo properties via
$env['envvar']and$property['name'](See
examples/flogo/simple/flogo.jsonfor usage in a flogo app)