@lotics/cli 0.321.7 → 0.321.9
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 +6 -6
- package/docs/build.md +1 -1
- package/docs/design.md +2 -2
- package/package.json +1 -1
package/docs/build.md
CHANGED
|
@@ -136,7 +136,7 @@ create_records {"table_id": "cake_line", "field_keys": ["order", "item", "quanti
|
|
|
136
136
|
Move the owner's rows through the app as their person would, each only as far as the stage the owner says it is at. Every Act runs as `act_<key>`, the one name, handed what it asks. A dry run walks the moves and files nothing; then press each paper Act for real, on one row the owner's stage allows or on an example row left at its last stage: what is left on a row is what the owner opens. Prove a rule by sending the write with `dry_run: true`; never switch a check off. Only an admin passes `as_member`: it shows a member's view and reads, which is how each person's screen is checked. What the shots and runs must show is `design/the-rubric`.
|
|
137
137
|
```
|
|
138
138
|
run_app_workflow {"app_id": "app_…", "alias": "act_start_baking", "inputs": {"record_id": "rec_…", "prepaid": 20}, "dry_run": true}
|
|
139
|
-
screenshot_app {"app_id": "app_…", "as_member": "<member id>"}
|
|
139
|
+
screenshot_app {"app_id": "app_…", "as_member": "<member id>", "pages": [{}, {"record_id": "rec_…"}]}
|
|
140
140
|
```
|
|
141
141
|
|
|
142
142
|
## 7. Hand over
|
package/docs/design.md
CHANGED
|
@@ -127,7 +127,7 @@ or its entity is read-only (`edit: false`); a stepped status never is, since Act
|
|
|
127
127
|
- `create` (boolean | list of alias (at least one)): The fields an add asks
|
|
128
128
|
- `columns` (list of (alias | Edit column)): Fields read after the row's title
|
|
129
129
|
- `label` (text): The register's name in the app's lists and tab strip
|
|
130
|
-
- `filters` (list of (alias | Tiered filter) (at most 3)): Fields the reader narrows by every day, beside the stage chips
|
|
130
|
+
- `filters` (list of (alias | Tiered filter | Listed filter) (at most 3)): Fields the reader narrows by every day, beside the stage chips
|
|
131
131
|
- `children` (list of (Tab | Reading | Export | Act | List) (at least one)): Its Tabs, band Readings, Exports and Acts over ticked rows or every row in view
|
|
132
132
|
- `key` (alias): Names the List among its siblings and in a Query's `list`
|
|
133
133
|
- `sort` (Sort key | list of Sort key (at least one)): The rows' order
|
|
@@ -197,7 +197,7 @@ or its entity is read-only (`edit: false`); a stepped status never is, since Act
|
|
|
197
197
|
## Look at it
|
|
198
198
|
|
|
199
199
|
After an apply, `screenshot_app` draws each app as its people see it — the register, and a record by its `path` or its `record_id`
|
|
200
|
-
(with a `path` on that record, such as one Section; `screen` for a later screen of a long one) — at a desk's width and a phone's, naming the columns a table left off at each width;
|
|
200
|
+
(with a `path` on that record, such as one Section; `screen` for a later screen of a long one), up to six `pages` in one call — at a desk's width and a phone's, naming the columns a table left off at each width;
|
|
201
201
|
`-o <dir>` saves the shots from the CLI. Beside them, `verdict` is what a write of the stored tree would be refused for
|
|
202
202
|
now, and its notes. Answer `design/the-rubric`, change the tree with `nodes`, and write again. To go back,
|
|
203
203
|
send the tree saved before the change as `body` with `app_id`, nulling an App prop stated since (`words`, `scope`,
|