@lotics/cli 0.321.33 → 0.321.35
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 +5 -0
- package/docs/workflow_steps.md +4 -0
- package/docs/working_in_a_workspace.md +4 -0
- package/package.json +1 -1
package/docs/design.md
CHANGED
|
@@ -203,6 +203,11 @@ callout, in the List's filter of what needs checking with how many rows hold it,
|
|
|
203
203
|
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
204
|
status, a category a select.
|
|
205
205
|
|
|
206
|
+
An issue is a promise that someone will act every time it stands: people and their agents see it on every row it holds.
|
|
207
|
+
Declare one only where the owner confirms each flagged case is a problem; a rule that flags rows nobody fixes trains
|
|
208
|
+
everyone to ignore the colour, real issues included. Where a flagged row may be accepted as it is (a price agreed by
|
|
209
|
+
exception), give the acceptance a field the formula reads, so accepting it clears the issue.
|
|
210
|
+
|
|
206
211
|
- An issue is a formula of the row stating `output_type`: `"boolean"` stands while true; `"text"` stands while not empty,
|
|
207
212
|
its words the sentence the reader sees — use it when the sentence must say what or how much ("Short 4 of 10").
|
|
208
213
|
Its label is its name. Put the moment it matters in the formula, so it clears itself when the work is done.
|
package/docs/workflow_steps.md
CHANGED
|
@@ -2178,6 +2178,10 @@ above. A provider's refusal carries the provider's own words.
|
|
|
2178
2178
|
| `data` | object | yes | |
|
|
2179
2179
|
| `display` | object | | Human-readable display values for select, member, and record link fields. Omitted from a workflow read whose body never looks at it. |
|
|
2180
2180
|
| `links` | object | | Each link field's linked rows with the title the cell carries, by field alias; `data` holds their ids. |
|
|
2181
|
+
| `issues` | object[] | | What the workspace marks as needing a person's action on this row, in its priority order, whatever fields were asked for; absent where the row holds none. |
|
|
2182
|
+
| `issues[].issue` | string | yes | |
|
|
2183
|
+
| `issues[].name` | string | yes | |
|
|
2184
|
+
| `issues[].says` | string | yes | |
|
|
2181
2185
|
| `locked` | boolean | | |
|
|
2182
2186
|
| `comment_count` | number | | How many comments the record holds. Omitted from a workflow read whose body never looks at it. |
|
|
2183
2187
|
| `comments` | object[] | | With `comments: true`: the newest first. |
|
|
@@ -89,6 +89,10 @@ under.
|
|
|
89
89
|
3. A question no app answers is `query_records` over one table: its rows, or with `aggregate` counts and sums grouped by a
|
|
90
90
|
field; `filters` is the grammar of both.
|
|
91
91
|
|
|
92
|
+
A row `query_records` or an app's query returns carries its issues when it holds any: what the
|
|
93
|
+
workspace marks as needing a person's action, in its priority order, whatever columns the read asked for. `get_workspace`
|
|
94
|
+
and `get_app` state how many rows hold each.
|
|
95
|
+
|
|
92
96
|
## A worked day
|
|
93
97
|
|
|
94
98
|
A customer asks for the status of order 1042, then the order is shipped:
|