We expect that one can easily change the states, so it means that NO mention to explicit next_state should be found anywhere in the state python file.
The idea is:
Do a large "merge" to get all changes from original project, that might require even rewritten project history: https://github.com/panoptes/POCS
Refer to a generic transition in python code, and expect the destination state to be defined in the state yaml file.
Example: call
tracking_ok_trigger
or
tracking_error_trigger in the code, and in the config yaml have something like:
We expect that one can easily change the states, so it means that NO mention to explicit next_state should be found anywhere in the state python file. The idea is:
tracking_ok_trigger
ortracking_error_trigger
in the code, and in the config yaml have something like:or