You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Example: call
tracking_ok_trigger
or
tracking_error_trigger
in the code, and in the config yaml have something like:or
The text was updated successfully, but these errors were encountered: