@lotics/cli 0.321.110 → 0.321.112
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 +4 -4
- package/docs/design.md +10 -6
- package/docs/document_templates.md +1 -1
- package/package.json +1 -1
package/docs/design.md
CHANGED
|
@@ -126,7 +126,7 @@ or its entity is read-only (`edit: false`); a stepped status is not, since Acts
|
|
|
126
126
|
|
|
127
127
|
- `entity` (alias, required): The table whose rows the List draws
|
|
128
128
|
- `create` (boolean | list of alias (at least one)): The fields an add asks
|
|
129
|
-
- `columns` (list of (alias | Edit column)): Fields read after the row's title, each drawn though no row holds it
|
|
129
|
+
- `columns` (list of (alias | Edit column)): Fields read after the row's title, in this order, each drawn though no row holds it
|
|
130
130
|
- `label` (text): The register's name in the app's lists and tab strip
|
|
131
131
|
- `filters` (list of (alias | Tiered filter | Listed filter)): Fields the reader narrows by every day, beside the stage chips
|
|
132
132
|
- `children` (list of (Tab | Reading | Act | List) (at least one)): Its Tabs, band Readings and Acts over ticked rows or every row in view
|
|
@@ -197,14 +197,18 @@ or its entity is read-only (`edit: false`); a stepped status is not, since Acts
|
|
|
197
197
|
|
|
198
198
|
## Issues
|
|
199
199
|
|
|
200
|
+
A row takes what the person has, in the order it arrives — a supplier's paper after the delivery, a payment before its
|
|
201
|
+
invoice, a price filled in later. What is missing or out of order is an issue on the row, never a refusal of the write;
|
|
202
|
+
refusal is kept for what must never happen and for the step that cannot be taken without a fact, which names it (an
|
|
203
|
+
invoice made without the buyer's tax code).
|
|
204
|
+
|
|
200
205
|
Whatever goes wrong on a row and needs a person to act — a line delivered short, a price missing, a customer over their
|
|
201
206
|
credit limit, a permit about to expire — is an issue its table declares in `records.issues`. A declared issue stands in
|
|
202
207
|
every app that draws its row, with no app stating it: first on the row's line (`+N` the others), in the record's callout (a count of child rows as pills on those rows), in the List's filter of what needs checking with how many rows hold it, and those rows first. It never makes an
|
|
203
208
|
app draw a row it did not, and never shows on an `Outside` page. What needs no one's action is no issue: a stage is the
|
|
204
209
|
status, a category a select. A record's callout says each issue by its label and what it means: a text issue's own sentence, a yes/no issue's field `description` — give a yes/no issue's field one, or its line shows the name alone.
|
|
205
210
|
|
|
206
|
-
|
|
207
|
-
Declare one only where the owner confirms each flagged case is a problem; a rule that flags rows nobody fixes trains
|
|
211
|
+
Declare an issue only where the owner confirms each flagged case is a problem: a rule that flags rows nobody fixes trains
|
|
208
212
|
everyone to ignore the colour, real issues included. Where a flagged row may be accepted as it is (a price agreed by
|
|
209
213
|
exception), give the acceptance a field the formula reads, so accepting it clears the issue.
|
|
210
214
|
|
|
@@ -261,7 +265,7 @@ Whether the build does the owner's work, answered by a call each, never from wha
|
|
|
261
265
|
4. Does each screen show the least its next step needs, each fact once, the signal that a step is due leading?
|
|
262
266
|
5. Is anything cramped at desk or phone width?
|
|
263
267
|
6. Is every paper and every exporting List's workbook made, those this kind of business sends unasked too, with no blank? Press each paper Act and read the file it files; prove a List's `export: true` with `run_app_query` and `export`.
|
|
264
|
-
7. Is each thing that must never happen in this business (a step taken before its approval, stock below zero, a double booking) refused on every write? Prove each with a write sent `dry_run: true` that is refused (`workflows/table-checks`).
|
|
268
|
+
7. Can each row be recorded with what the person has now, its gap an issue, while only the step that needs the fact refuses? Is each thing that must never happen in this business (a step taken before its approval, stock below zero, a double booking) refused on every write? Prove each with a write sent `dry_run: true` that is refused (`workflows/table-checks`).
|
|
265
269
|
|
|
266
270
|
A failed answer is a change to the tree, or a gap named to the owner.
|
|
267
271
|
|
|
@@ -453,8 +457,8 @@ its exception as a formula's yes/no in a Reading's `where` (what is short), neve
|
|
|
453
457
|
status chips already count, nor the overdue rows the register's summary line counts from `records.due` — then at most the mix (`by` a field) and the movement (`by` a date), varied by job. A movement over a date is stated, never defaulted; so is a sum, but for the one a status register with a money figure leads with by default: that figure over its open rows, titled by them ("Price (open)"). A register with no such figure and no single select to split by gets no default band.
|
|
454
458
|
A grid (`by` and `across`) reads on a Sheet. A Sheet — a View of Readings at the App's root, beside its Lists or alone —
|
|
455
459
|
answers one owner's question across jobs, each Reading windowed by the reader's period (the App's `period`), and a
|
|
456
|
-
List on it hands over the rows to act on.
|
|
457
|
-
|
|
460
|
+
List on it hands over the rows to act on. A figure stated per party (owed, overdue, short) opens on the rows that make it,
|
|
461
|
+
listed on that party's page and adding up to it. Many Readings stand on several Sheets, each a View the reader picks. A question one app's rows answer goes on a Sheet there; one spanning apps gets a small app of its own. A Record's Readings read its own child rows. Sums of each row's child rows are a Tab's `totals`. Worked: `examples/approval`, `examples/dashboard`.
|
|
458
462
|
|
|
459
463
|
#### Funnel
|
|
460
464
|
|
|
@@ -183,7 +183,7 @@ Here `code`, `customer` and `total` are fields of the record and `lines` is its
|
|
|
183
183
|
`{{$line.description}}` … `{{END-FOR line}}`. A link whose partner is not paired reaches no rows from the record, and
|
|
184
184
|
a loop printing a field of each of its items is refused, naming `pair`.
|
|
185
185
|
|
|
186
|
-
Every List the record draws and the template names (an html template's variables, a Word template's markers) hands its
|
|
186
|
+
Every List the record draws and the template names (an html template's variables, an Excel template's declared variables, a Word template's markers) hands its
|
|
187
187
|
rows, each List's `where` applied; a List the template does not name is not read. A List that only reads hands them under its
|
|
188
188
|
`key` (the table's alias where it states none), and a List that sums a number hands the sums under `<name>_totals`, one
|
|
189
189
|
entry per number the List draws as a column or as the table's figure. A `where` bound may be `{ "record": "<field>" }`,
|