Skip to content

Commit 4c44bdf

Browse files
committed
docs(skills): the objectstack-ui list-views rule teaches kanban.lanes
The kanban example shows `lanes`, the stored option values to draw in that order, and the note under it says it is a choice of lanes, not a record filter (an unlisted value lands in `Uncategorized`; filter the view to keep records off the board) and that a non-option or repeated value fails `os validate`. Paid for by folding two ADR-0047 renderer notes into the code comments they repeat. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L9qibz4G9FrLR4TRExx6gn
1 parent c2f1483 commit 4c44bdf

1 file changed

Lines changed: 8 additions & 10 deletions

File tree

‎skills/objectstack-ui/rules/list-views.md‎

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -117,15 +117,15 @@ toggles the user combines at runtime:
117117

118118
```typescript
119119
userFilters: {
120-
element: 'dropdown', // 'dropdown' | 'tabs' | 'toggle'
120+
element: 'dropdown', // 'dropdown' | 'tabs' ('toggle' is deprecated)
121121
fields: [
122122
{ field: 'status' }, // options/labels inferred from field def
123123
{ field: 'priority', showCount: true },
124124
],
125125
},
126126

127127
// Runtime visualization whitelist (Airtable "Appearance → Visualizations"):
128-
appearance: { allowedVisualizations: ['grid', 'kanban', 'gallery'] },
128+
appearance: { allowedVisualizations: ['grid', 'kanban', 'gallery'] }, // one entry = locked, no switcher
129129
```
130130

131131
Rules:
@@ -150,11 +150,6 @@ Rules:
150150
so most views need no filter elements at all.
151151
- `userFilters: { element: 'dropdown' }` (no `fields`) is valid shorthand:
152152
the renderer fills the field list from the object's select/boolean fields.
153-
- `element` is `dropdown` or `tabs`; `toggle` is **deprecated** (ADR-0047 §3.4a)
154-
— it stays in the enum for back-compat rendering, but author `dropdown`/`tabs`.
155-
- The visualization switcher renders as a compact dropdown in the toolbar's
156-
right cluster. Authors only control the `allowedVisualizations` whitelist;
157-
a single-entry whitelist locks the visualization (no switcher).
158153

159154
### Toolbar Search (`searchableFields`, ADR-0061)
160155

@@ -272,16 +267,19 @@ top-level `groupBy`**. The top-level `columns` is required on every list view
272267
data: { provider: 'object', object: 'project_task' },
273268
columns: ['title', 'assignee', 'priority'], // required on every list view
274269
kanban: {
275-
groupByField: 'status', // one board column per select option
270+
groupByField: 'status', // a select field — one lane per option
271+
lanes: ['todo', 'in_progress', 'review'], // option VALUES to draw, in this order
276272
summarizeField: 'estimate_hours', // optional — summed at the top of each column
277273
columns: ['title', 'assignee', 'priority'], // fields shown on each card
278274
},
279275
sort: [{ field: 'priority', order: 'desc' }],
280276
}
281277
```
282278

283-
> **Key rule:** `kanban.groupByField` should be a `select` type with
284-
> well-defined options. Each option becomes a column on the board.
279+
> `lanes` chooses the lanes and their order, not the records: a record whose
280+
> value is unlisted lands in `Uncategorized`, so filter the view to keep records
281+
> off the board. Omit it to draw every option in its own order; a value that is
282+
> not an option, or listed twice, fails `os validate`.
285283
286284
---
287285

0 commit comments

Comments
 (0)