Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support keyword nil in expression #167

Closed
lixingwang opened this issue Apr 12, 2018 · 0 comments
Closed

Support keyword nil in expression #167

lixingwang opened this issue Apr 12, 2018 · 0 comments
Assignees
Milestone

Comments

@lixingwang
Copy link
Contributor

lixingwang commented Apr 12, 2018

I'm submitting a ... (check one with "x")

[] bug report => search github for a similar issue or PR before submitting
[x] enhancement request
[] feature request
[] support request
[] general question

Current behavior (how does the issue manifest):
Today, there is no way to check whether the property's value is empty or it non-exist.
In order to support this case. we plan to support != nil expression.
Expected behavior:
Introduce a keyword nil in expression, it representative empty value, just like Golang nil.
Such as $activity[rest].content.id !=nil or activity[rest].content.id == nil
Minimal steps to reproduce the problem (not required if feature enhancement):

What is the motivation / use case for changing the behavior?

Please tell us about your environment (Operating system, docker version, browser & verison if webui, etc):

Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.X.X

Additional information you deem important (e.g. issue happens only occasionally):

@lixingwang lixingwang self-assigned this Apr 12, 2018
@lixingwang lixingwang added this to the 0.5.4 milestone May 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant