cr-connect-workflow/package-lock.json at 2e9205fa08d9f661d81a80af4c6dd3f307fdf2b2 - cr-connect-workflow - Status.im Repos

sartography/cr-connect-workflow

mirror of https://github.com/sartography/cr-connect-workflow.git synced 2025-02-23 05:08:32 +00:00

Dan 5e54c90b47 "Reset" should not mean "re-start". Calling the reset_workflow script will now set the workflow to an "unstarted" state with no outstanding tasks, no json-state structure stored. The workflow is not yet running.

Also:
* Assured that arguments are consistent (we always seem to use workflow_spec_id, so I made sure we use that consistently.
* Don't require named parameters - so it's cool to call it like: reset_workflow('my_workflow_id')
* Task Actions (ie create, assign, etc...) are now an enumeration in the models, and not static variables on Workflow Service, so we can reference them consistently from anywhere.
* Removed some repetitive code
* Always try to validate as much as possible in the scripts to save folks time debugging.
*

2022-04-15 15:36:23 -04:00

7 lines

98 B

JSON

Raw Blame History

 {
   "name": "cr-connect-workflow",
   "lockfileVersion": 2,
   "requires": true,
   "packages": {}
 }