@lotics/cli 0.293.0 → 0.294.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/src/cli.js +34 -18
- package/docs/workflow_steps.md +3694 -0
- package/docs/workflows.md +3 -2
- package/package.json +1 -1
package/docs/workflows.md
CHANGED
|
@@ -64,8 +64,9 @@ await send_email({
|
|
|
64
64
|
| return | `return({ status: "success" \| "error", message: <expr>, field_errors: { ... }? });` |
|
|
65
65
|
| validate | `validate({ checks: [{ fail_when: <expr>, field_key: "...", message: <expr> }, ...] });` |
|
|
66
66
|
|
|
67
|
-
Every step's inputs, the values each takes and its answer: `lotics tools <name>` prints them
|
|
68
|
-
|
|
67
|
+
Every step's inputs, the values each takes and its answer: `lotics tools <name>` prints them; the steps only a body
|
|
68
|
+
runs — a connection's, a mail's — are all in `workflow_steps`. `query_integration_tools` lists the workspace's
|
|
69
|
+
connections and the steps each opens.
|
|
69
70
|
|
|
70
71
|
`return` is a call, not a JavaScript `return` statement. `validate` ends the workflow with an error
|
|
71
72
|
when a check's `fail_when` is truthy; the check's `field_key` names the control its message lands on —
|