Settings pages edit through TanStack Form #1695

Closed
opened 2026-10-27 13:41:25 +00:00 by sam · 0 comments
Owner

Every settings page edits its control-plane resource through a TanStack form owned by the settings store (one per kind, surviving navigation) instead of mutating drafts. Fields use the shadcn-vue Field components; the save bar, review drawer, was-hints and leave-page guard read form state; validation comes from draftValidators through the form. Done when no page reads store.drafts, typecheck and task check pass, and the container runtime page shows the max_uptime warning above the field.

Close reason

Shipped in cc2f3a46


Imported from beads archie-core-zfu9t · GitHub #1860 · type feature · priority P1 · created 2026-10-26 · closed 2026-10-26

Every settings page edits its control-plane resource through a TanStack form owned by the settings store (one per kind, surviving navigation) instead of mutating drafts. Fields use the shadcn-vue Field components; the save bar, review drawer, was-hints and leave-page guard read form state; validation comes from draftValidators through the form. Done when no page reads store.drafts, typecheck and task check pass, and the container runtime page shows the max_uptime warning above the field. ### Close reason Shipped in cc2f3a46 --- _Imported from beads `archie-core-zfu9t` · GitHub #1860 · type feature · priority P1 · created 2026-10-26 · closed 2026-10-26_
sam added the highfeature labels 2026-10-27 13:41:25 +00:00
sam self-assigned this 2026-10-27 13:41:25 +00:00
sam closed this issue 2026-10-27 13:41:25 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1695