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

Inspect results of parent subflows in edge conditions #16

Open
fridex opened this issue Nov 8, 2016 · 1 comment
Open

Inspect results of parent subflows in edge conditions #16

fridex opened this issue Nov 8, 2016 · 1 comment

Comments

@fridex
Copy link
Member

fridex commented Nov 8, 2016

Currently, one of the major limitations Selinon has is the fact that results of parent sub-flows cannot be used in conditions. It would be nice to include such capability.

@fridex
Copy link
Member Author

fridex commented Nov 8, 2016

This might be confusing in many cases since flows can have multiple tasks of a same type. A solution would be to include flags:

  • any - similar to Python's any() - a condition is evaluated as true if any of parent tasks resutls (from parent subflow) meet given condition
  • all - again, similar to Python's all() - a condition is evaluated as true if all parent tasks results (from parent subflow) meet given condition
  • filter - this would propagate all parent tasks which results meet given condition, the ones that do not accept condition are omitted from parent in scheduled task
  • every - this would schedule multiple tasks, each task would have exactly one parent task from parent subflow as if parent flow would be a parent task

Further inspection needed - e.g. what to do in more complex situations (possibly stick with all permutations as now with multiple parent of a same type).

@fridex fridex changed the title Inspect results of parent subflows Inspect results of parent subflows in edge conditions Apr 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant