- ConversionResult: already two-line layout (value + label/symbol) - app.css: responsive grid (1/2/3 cols at <480/480-899/≥900px) - uniformFontSize.ts: JS-measured uniform font size per grid - config.ts: remove MIN_COLUMN_WIDTH, grid is now CSS-only - BACKLOG.md: remove resolved 'allow renaming unit/group IDs' item Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.1 KiB
humor-units Backlog
Issues and improvements to address eventually. Not blockers.
Bugs
(none yet)
Improvements
UI: "Clear" button hover feedback in light/Dan mode
In dark mode the "Clear" button text lightens on hover, giving visual feedback. In light mode and Dan mode it currently does nothing visible. Should have a matching subtle highlight (e.g. text darkens, underline appears, or border darkens).
Admin: tooltips / descriptions for units
Allow users to attach an optional description string to each unit. On the front end,
show it as a tooltip when hovering over the unit name or symbol. A single description
field is sufficient — no need to distinguish between tooltip text and description text.
Data shape change: add optional description?: string to the Unit type.
Admin: group sort order (alphabetical vs. defined)
Per-group setting controlling whether units are displayed on the front end in:
- Defined order — the order they appear in
units.json(current implicit behaviour) - Alphabetical order — sorted by label at render time
Data shape change: add optional sortOrder?: 'defined' | 'alpha' to the Group type
(default: 'defined').
Admin: unsaved-form guard on "Add Unit" / "Add Group"
If the user is in the middle of filling out a create/edit form and clicks "+ Add Unit" or "+ Add Group", the current form should be auto-saved before opening the new one. If the save fails (e.g. missing required field), highlight the erroring field and block navigation until it is resolved — don't silently discard the in-progress work.
Admin: configure YOLO mode label and description via admin page
The YOLO mode toggle label and description are currently configurable only by editing
data/config.json directly (yoloLabel, yoloDescription fields). Add a settings
section to the admin page where these can be edited in-browser and saved via a new
PUT /admin/api/config endpoint.
Add a "Delete" option to the bulk action dropdown so multiple units can be deleted at once. Should show a confirmation dialog listing the units to be deleted before committing.