Lists: typed, schema-driven row editor (replaces the freeform JSON box)

[Adron]

Stacked PR — 2 of 3

issue-21-typed-row-editor → base issue-18-column-builder (PR #161) → which bases on issue-17-list-schema-service (PR #143). Merge the stack bottom-up: #143, #161, then this, then #22.

What this adds

Rows on a list with columns are added and edited through a form generated from its live schema instead of a raw-JSON box:

Type	Control
text / email / url / tel	single-line box (email and URL validated locally)
textarea	multi-line box
number	numeric box, validation.step shown as a hint
boolean	True/False dropdown — plus Neither (null) when the column is optional
date	date picker → YYYY-MM-DD
datetime	date picker + HH:MM → ISO
select / priority	single select (priority over its four values)
multiselect	checkbox set → a real JSON array

defaultValue pre-fills new rows; placeholder, helpText, visible and displayOrder are honoured; hidden columns fold behind a toggle so a required hidden column is still reachable. Conditional-visibility rules are evaluated client-side by ListFieldConditionEvaluator — the only place they are ever evaluated, since the server stores a condition and never applies it.

The grid no longer prints JSON: one labelled cell per visible column, a checkbox for boolean, chips for multiselect, an em dash where the row has no value. Row data is keyed by each column's key throughout.

The raw-JSON hatch stays — the only editor for a schema-less list, and one checkbox (“Edit rows as raw JSON”) away on a schema'd one.

Live evidence (probed today, 2026-09-16)

All throwaway lists were titled ZZ claude-probe … and deleted; a closing GET /api/lists shows only the account's pre-existing New list.

1. A row write REPLACES rowData, it does not merge. A PUT carrying {"title":"replaced"} left the row holding only title — five other values, an unknown key included, gone. So the form re-sends every key it knows about, and any field the user didn't touch is echoed back as the exact JsonElement the server gave us, which keeps values the form can't fully model (a naive datetime, a number stored as a string, a nested object) byte-identical. A blank optional column the row never had is still left out rather than padding rowData with nulls; clearing a stored value sends an explicit null.
2. Unknown keys are accepted and preserved on a schema'd list — including nested objects. They are what a destructive column rebuild leaves behind, so the grid names them (“No column for: …”) and the editor says it is keeping them rather than pretending they're gone.
3. Types are enforced on write (each message captured live): "true" in a boolean column → 422 Done must be true or false; a comma string in a multiselect → Tags must be an array; 09/16/2026 → Due must be a valid date; a select value off-list → Status must be one of: open, closed. The exceptions: a number accepted as "7" — and then its own min/max check is silently skipped, which is exactly why the form sends a real number — and priority, which is not validated against its four values at all.
4. 422 carries details:[{field,message}], up to eight at once, field being the column key and the message using its label. EnsureSuccessAsync flattens that to “Validation failed”, so the two row writes now throw ListRowValidationException and each message lands on its control. Required, email/url shape, number parse, min/max, minLength/maxLength and pattern are checked before the round trip.
5. GET /api/lists/{id}/data omits each row's listId (and rowNumber), which ListDataRow.ListId's required turns into a JsonException right through GetListDataAsync — the crash Lists: viewing any list that has rows throws — ListDataRow.ListId is required but the API doesn't send it #144/PR fix(lists): viewing a list with rows threw — ListId was required but absent #146 fixes. ListDataRow.cs is that PR's, so this branch doesn't touch it: reads go through a new tolerant GetListRowsAsync that maps rows by hand and fills listId in from the request. Dependency: once fix(lists): viewing a list with rows threw — ListId was required but absent #146 lands, GetListDataAsync works again and ListDataRow.Version becomes available.
6. version is not optimistic concurrency. Sending a deliberately stale version: 1 on a row PUT still answered 200 and bumped the row to 4 — the server ignores it. So there is nothing to hook up yet, and fix(lists): viewing a list with rows threw — ListId was required but absent #146's Version buys a display value rather than a conflict check.
7. End-to-end with the real view-model: a throwaway net10.0 console project <Compile Include>-ing the model and row-field files by absolute path produced a twelve-type row payload — 201, stored exactly as sent — then an edit payload carrying an unknown key and a nested object — 200, both intact. It also confirmed the local pre-flight messages, the tri-state boolean options, the status=closed → “Why closed?” visibility flip, and the grid's cell kinds.

Left unverified / deliberately out

• No WPF rendering check is possible from macOS. dotnet build passes in Debug and Release. The new controls use theme brushes and 3–4px corners, but two want eyes on Windows: the templated ComboBox drop-down (from Lists: schema column form builder (12 field types) #161) and the DatePicker, whose calendar popup keeps its platform look — only the field itself is painted from the theme. If that reads wrong in dark mode, the fix is a templated date box, not a colour override.
• Datetimes are written as naive ISO (2026-09-16T14:30:00, accepted live) and never timezone-shifted, so a value entered is the value stored; a stored value with a Z that the user doesn't touch is re-sent verbatim.
• Row pagination is still the first 50 (unchanged); #21 didn't ask for more.

Closes #21

🤖 Generated with Claude Code