@lotics/app-sdk 0.82.2 → 0.82.3
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/docs/workflows.md +8 -3
- package/package.json +1 -1
package/docs/workflows.md
CHANGED
|
@@ -632,9 +632,14 @@ The rules that are easy to get wrong because the failing code looks correct.
|
|
|
632
632
|
spelling. Start that binding from the first array instead of seeding it `[]`. Appending single
|
|
633
633
|
**items** (`xs.push(item)`) works on a bare `[]` seed.
|
|
634
634
|
- **A mutation on the trigger table of an `after_*` workflow can re-trigger itself** — a lint
|
|
635
|
-
warning, not an error. Gate it on `trigger.change_origin
|
|
636
|
-
|
|
637
|
-
|
|
635
|
+
warning, not an error. Gate it on `trigger.change_origin` — the originating write's origin —
|
|
636
|
+
and name every origin you mean to let through, rather than testing for one. `member` is a
|
|
637
|
+
person in the browser and **only** that: the same edit made over MCP, the CLI, or a direct API
|
|
638
|
+
call arrives as `api_client`, and one made by the chat agent as `chat_agent`. A gate meaning
|
|
639
|
+
"someone did this by hand" is
|
|
640
|
+
`includes(["member", "chat_agent", "api_client"], trigger.change_origin.type)`. Not
|
|
641
|
+
`runtime.change_origin`: that is the execution's own origin, always `table_workflow` here, so
|
|
642
|
+
it discriminates nothing.
|
|
638
643
|
|
|
639
644
|
## The bright line
|
|
640
645
|
|