@lotics/cli 0.321.84 → 0.321.86
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 +12 -17
- package/docs/data_model.md +4 -16
- package/docs/workflows.md +3 -1
- package/package.json +1 -1
package/docs/data_model.md
CHANGED
|
@@ -91,23 +91,11 @@ Anything that imports, reconciles or de-duplicates has to decide identity, and w
|
|
|
91
91
|
comparing displayed text — which is how one company arrives three times under three spellings. Name the key: a reference
|
|
92
92
|
number, a tax id, a link plus a period. Then match on record ids and option aliases, never on rendered labels.
|
|
93
93
|
|
|
94
|
-
##
|
|
95
|
-
|
|
96
|
-
A row that belongs to another by what it holds states a link the platform fills (`reference/link`, `fill`): a lesson to
|
|
97
|
-
its teacher's month, a reading to the price in force on its day, a line arriving with a code to the row that code names.
|
|
98
|
-
The link's `options_where` reads the row's own fields as `{ "$expr": "record.<field>" }`, and the platform keeps the link
|
|
99
|
-
as either row changes:
|
|
100
|
-
|
|
101
|
-
```json
|
|
102
|
-
"month": { "type": "link", "label": "Month", "table": "teacher_months", "multi": false, "pair": "lessons", "fill": true,
|
|
103
|
-
"options_where": { "node_type": "group", "logic": "and", "children": [
|
|
104
|
-
{ "node_type": "condition", "field_key": "teacher", "operator": "has_any_of", "value": { "$expr": "record.teacher" } },
|
|
105
|
-
{ "node_type": "condition", "field_key": "month", "operator": "on", "value": { "$expr": "record.starts_at" } } ] } }
|
|
106
|
-
```
|
|
94
|
+
## A row that belongs to another by its VALUES holds a link
|
|
107
95
|
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
96
|
+
An adjustment belongs to its person's month, a payment to its customer's statement: the row holds an ordinary link to
|
|
97
|
+
that row, set when the row is made — by the screen that adds it under its parent, or by a table workflow that finds the
|
|
98
|
+
parent from the row's values. A rollup through the link then reads live, and the link stays a person's to correct.
|
|
111
99
|
|
|
112
100
|
## A stage's moment is a date on the row
|
|
113
101
|
|
package/docs/workflows.md
CHANGED
|
@@ -648,7 +648,9 @@ nothing, and recognises what exists by the identity the input carries — so a c
|
|
|
648
648
|
adds nothing. `match` is the record's identity, `{ field_key: value }`, and must be exactly a uniqueness
|
|
649
649
|
its table declares: one field marked `unique`, or the fields of one of the table's `unique` sets together
|
|
650
650
|
(text, number, date, single select and one-row link fields). A `match` that is no declared uniqueness is
|
|
651
|
-
refused, naming what the table does declare
|
|
651
|
+
refused, naming what the table does declare: where the body is saved when its table and fields are written
|
|
652
|
+
out, at run otherwise. A table cannot lose a uniqueness a stored `save_record` matches on: declare the new
|
|
653
|
+
one beside it, move the workflows to it, then take the old one away. A live record carrying the match is found and only the cells
|
|
652
654
|
of `set` that differ are written; none is found and it is added with `match` and `set`. `add_to` appends
|
|
653
655
|
to a files, multi-select or many-link field and keeps what it holds.
|
|
654
656
|
|