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

Check steps and flow #23

Open
uwegeercken opened this issue Aug 25, 2020 · 2 comments
Open

Check steps and flow #23

uwegeercken opened this issue Aug 25, 2020 · 2 comments

Comments

@uwegeercken
Copy link

Problem description

The developer needs a way of checking individual steps or the complete flow. As typically names for fields, variables, files, functions and other parts change during development, the developer today only detects an error when the flow runs.

Flows can have long runtimes and it is not productive and efficient to detect errors only when the flow runs. It should be as error-free as possible before it is run.

Preferred solution

Add functionality to check the flow. When the user selects this feature, the flow and all steps are checked as appropriate. One could maybe also configure the flow to always check before it runs.

  • check variable references
  • check field references
  • check file path and name references
  • check spelling in content where possible: evaluate functions, dicts, lists
  • check suspicious settings like e.g. no output hop but two error hops
  • check absence of mandatory information
  • check missing or invalid connections between steps
  • others

Some results are typically errors which prohibit the flow from running. Others are more like warnings where the flow does run but a change would be recommended or the settings are at least suspicious or something e.g. is deprecated.

@uwegeercken
Copy link
Author

as discussed, additionally check the presence of modules which are referenced in the flow. this should also check if variables, services referenced from modules are present.

@uwegeercken
Copy link
Author

there could (maybe) be an option in the run dialog to check the flow before running it. but this is just an idea.

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