@lotics/cli 0.312.10 → 0.312.11

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.
@@ -167,7 +167,7 @@ inside it. Each type takes only its own:
167
167
  creation once, `"updated_at"` re-stamps on every update; the field is then read-only, takes no
168
168
  `default_value`, and holds only the `date` and `datetime` formats.
169
169
  - **boolean** — `default_value?` (`true` | `false`).
170
- - **select** — `options` `[{ name, color?, mark? }]`, `multi?`, `default_value?`.
170
+ - **select** — `options` `[{ name, color?, mark? }]`, `multi?`, `default_value?`. An option stated without a `color` gets one no sibling option holds.
171
171
  - **select_member** — `multi?`, `default_value?` (member ids).
172
172
  - **select_record_link** — `table_id`, `display_field_keys?`, `sync_both_ways?`, `cardinality?`,
173
173
  `paired_field_name?`, `paired_field_display_field_keys?`. Without `display_field_keys` a link shows
@@ -275,6 +275,8 @@ properties as `add_fields`, plus what only an update does:
275
275
  key (its name also resolves); a rename keeps every record's value. `mark` is the option's brand
276
276
  (`{ kind: "brand", name: "tiktok" }`) or kit glyph (`{ kind: "icon", name: "wrench" }`), drawn in
277
277
  place of its colour dot — every option of a field has one or none does, so marking sets them all
278
- in one call and `mark: null` on each clears them.
278
+ in one call and `mark: null` on each clears them. `distinct_option_colors: true` re-colours a
279
+ select so every option holds its own: the first option of each colour keeps it, the rest take
280
+ colours no option holds.
279
281
  - A link's `sync_both_ways: false` disconnects the pair; a new `table_id` re-points it and clears its
280
282
  record data; `cardinality` is `"one"` for the child side of a parent-child pair, `"many"` for peers.
package/docs/examples.md CHANGED
@@ -58,6 +58,7 @@ Every key: the `model` reference, at the pages each section names under **Keys**
58
58
  "alias": "visits",
59
59
  "name": "Service visits",
60
60
  "icon": "calendar",
61
+ "theme": {"color": "emerald"},
61
62
  "entity": "service_visit",
62
63
  "register": {
63
64
  "columns": ["engineer", "job"],
@@ -149,6 +150,7 @@ Every key: the `model` reference, at the pages each section names under **Keys**
149
150
  "alias": "dispatch",
150
151
  "name": "Dispatch",
151
152
  "icon": "wrench",
153
+ "theme": {"color": "sky"},
152
154
  "entity": "service_visit",
153
155
  "register": {
154
156
  "columns": ["job"],
@@ -326,6 +328,7 @@ Every key: the `model` reference, at the pages each section names under **Keys**
326
328
  "alias": "lich_truc",
327
329
  "name": "Lịch trực",
328
330
  "icon": "users",
331
+ "theme": {"color": "indigo"},
329
332
  "entity": "nha_si",
330
333
  "register": {
331
334
  "filters": ["chuyen_mon"],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.312.10",
3
+ "version": "0.312.11",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {