Generic frontend renderer for scalar configuration fields #137
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: sam/archie#137
Reference in new issue
Block a user
Replace settings.js's hardcoded row(...) calls for scalar/bool/int/enum/duration fields with a renderer that walks the backend's sections/fields schema and builds the section cards, labels, and edit affordances from the descriptor alone -- the frontend must not know that containers.max_concurrency is an int or which card it belongs in. Structured fields (repositories, models, providers maps) are out of scope here and keep their existing bespoke rendering, tagged type=structured so the generic renderer skips them without special-casing each key.
Close reason
settings.js renders identity/budgets/storage/web cards generically from cfg.schema sections (schemaCards()), replacing identityCard/budgetsCard/storageCard/webCard/pullPolicyLabel -- label, type, description, editability, and options all come from the backend descriptor. config-row.js gained enum edit support (select from opts.options), an editable:false branch distinct from locked rows, and a hint tooltip carrying the field's description. Structured sections (repositories, models & providers) are unaffected -- still rendered by their existing bespoke functions, reserved for b6ew.4. Not visually verified in a live browser (needs a full daemon+forge+NATS stack); verified via unit tests mirroring the existing config-row.test.js patterns and Go contract tests.
Imported from beads
archie-core-b6ew.3· GitHub #693 · type feature · priority P2 · created 2026-09-02 · closed 2026-09-02