@lotics/cli 0.251.0 → 0.252.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 +414 -291
- package/docs/building_an_app.md +6 -1
- package/package.json +1 -1
package/docs/building_an_app.md
CHANGED
|
@@ -81,7 +81,12 @@ whole, and a generated workflow body is rewritten too, with the text it replaced
|
|
|
81
81
|
`src/components/` (seeded where it is absent, never rewritten), and the body of an act's own
|
|
82
82
|
`workflow` — only the guard region at its top, between the `<lotics:guards>` markers, is the
|
|
83
83
|
generator's. The manifest is reconciled by ownership — the generator's aliases replaced, the ones
|
|
84
|
-
it retired removed, the ones you added kept — then codegen and `app check` run.
|
|
84
|
+
it retired removed, the ones you added kept — then codegen and `app check` run. A generated
|
|
85
|
+
workflow is declared with the inputs it reads and the `outputs` its return hands back, so a
|
|
86
|
+
contract an earlier generation bound is replaced at the next deploy; your own act's `workflow`
|
|
87
|
+
keeps the outputs the server derived from your body. That body follows the guard region, which
|
|
88
|
+
already declares `i` and, on one record, reads it into `row` by `i.record_id`: reuse them, never
|
|
89
|
+
declare them again.
|
|
85
90
|
|
|
86
91
|
**Nothing is pushed.** What the live app RUNS changes at `lotics app deploy` and nowhere else: the
|
|
87
92
|
bundle production serves was built against the bindings it has, so a regeneration that replaced a
|