webui(base): form controls from the component spec #363

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

README section 4. Duration input (Go duration conversion only at the API boundary), byte size input (decimal MB, stores bytes), input with unit, stepper, labelled toggle with risky variant, segmented control (radiogroup, arrow keys), secret reference row with resolved/not-found status, chip input. Build on existing shadcn-vue primitives in components/ui.

Acceptance criteria

Each control has node tests for its conversion/keyboard logic; accessible names and role=switch/radiogroup verified.

Notes

Maintainer 2026-09-25: no Akaza UI, stay on shadcn-vue/reka-ui. Custom components live in the sibling archie-component-registry repo (shadcn-vue registry) and are installed via the CLI. Stock: number-field = stepper, tags-input = chip input, switch = toggle, input-group = unit suffix. Registry: duration-input, byte-size-input, segmented-control (reka RadioGroup), secret-reference.
Never hand-edit ui/src/components/ui; everything there arrives via npx shadcn-vue add.
PARTIAL delivery, merged e86c9e08. duration-input and byte-size-input now have module tests in ui/test/ (+9; suite 124 pass / 0 fail), covering the Go-duration conversion and the decimal-MB -> bytes conversion. Mutation-verified rather than red-first: flipping BYTES_PER_MB 1_000_000 -> 1_048_576 fails all three byte-size tests, and dropping 'ms' from parseGoDuration's unit regex fails the duration tests ('500ms' -> null). The tests can fail for an interesting reason.
The other six controls cannot be tested with the existing harness, so this bead's acceptance is NOT fully met and it stays open -- see the harness bead filed for it.
Deliberately left untested, with evidence: formatGoDuration(0.5) returns '0.5ms' where Go prints '500us' (below 1ms, unreachable from the pages' unit selectors); parseGoDuration accepts out-of-order and duplicate units ('1s30m', '1m1m') where Go parity is unverified.
Acceptance reduced per the merged harness decision (docs/development/frontend-ui.md, from 7svn): module-level tests are the standard for archie-authored logic. duration-input and byte-size-input keep their module tests. The six SFC-bound controls are covered upstream -- number-field, switch, segmented-control and tags-input by reka-ui's own per-component Vitest+axe suites, and input-group/secret-reference are not reka components but archie layout whose substance is one v-if/aria-passthrough, arriving content-pinned via the registry CLI.

Close reason

Closed


Imported from beads archie-core-micl.4 · GitHub #1007 · type task · priority P1 · created 2026-09-25 · closed 2026-09-29

README section 4. Duration input (Go duration conversion only at the API boundary), byte size input (decimal MB, stores bytes), input with unit, stepper, labelled toggle with risky variant, segmented control (radiogroup, arrow keys), secret reference row with resolved/not-found status, chip input. Build on existing shadcn-vue primitives in components/ui. ### Acceptance criteria Each control has node tests for its conversion/keyboard logic; accessible names and role=switch/radiogroup verified. ### Notes Maintainer 2026-09-25: no Akaza UI, stay on shadcn-vue/reka-ui. Custom components live in the sibling archie-component-registry repo (shadcn-vue registry) and are installed via the CLI. Stock: number-field = stepper, tags-input = chip input, switch = toggle, input-group = unit suffix. Registry: duration-input, byte-size-input, segmented-control (reka RadioGroup), secret-reference. Never hand-edit ui/src/components/ui; everything there arrives via npx shadcn-vue add. PARTIAL delivery, merged e86c9e08. duration-input and byte-size-input now have module tests in ui/test/ (+9; suite 124 pass / 0 fail), covering the Go-duration conversion and the decimal-MB -> bytes conversion. Mutation-verified rather than red-first: flipping BYTES_PER_MB 1_000_000 -> 1_048_576 fails all three byte-size tests, and dropping 'ms' from parseGoDuration's unit regex fails the duration tests ('500ms' -> null). The tests can fail for an interesting reason. The other six controls cannot be tested with the existing harness, so this bead's acceptance is NOT fully met and it stays open -- see the harness bead filed for it. Deliberately left untested, with evidence: formatGoDuration(0.5) returns '0.5ms' where Go prints '500us' (below 1ms, unreachable from the pages' unit selectors); parseGoDuration accepts out-of-order and duplicate units ('1s30m', '1m1m') where Go parity is unverified. Acceptance reduced per the merged harness decision (docs/development/frontend-ui.md, from 7svn): module-level tests are the standard for archie-authored logic. duration-input and byte-size-input keep their module tests. The six SFC-bound controls are covered upstream -- number-field, switch, segmented-control and tags-input by reka-ui's own per-component Vitest+axe suites, and input-group/secret-reference are not reka components but archie layout whose substance is one v-if/aria-passthrough, arriving content-pinned via the registry CLI. ### Close reason Closed --- _Imported from beads `archie-core-micl.4` · GitHub #1007 · type task · priority P1 · created 2026-09-25 · closed 2026-09-29_
sam added the hightask labels 2026-10-27 13:36:01 +00:00
sam self-assigned this 2026-10-27 13:36:01 +00:00
sam closed this issue 2026-10-27 13:36:01 +00:00
sam added a new dependency 2026-10-27 13:41:56 +00:00
sam added a new dependency 2026-10-27 13:41:56 +00:00
sam added a new dependency 2026-10-27 13:41:57 +00:00
sam added a new dependency 2026-10-27 13:41:58 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#363