Repository navigation
Replace free-text unit inputs with segmented controls for measurement units #18
Description
In several configuration forms, fields that require a unit of measure (e.g. power unit: W, kW or hash rate unit: GH/s, TH/s) are currently rendered as free-text inputs.
This creates two problems:
- it is error-prone, since users can type inconsistent or invalid values (e.g. w, KW, kw)
- it is ambiguous, as the field looks like a numeric input rather than a unit selector, which can confuse users on first use
Proposed solution
Replace these free-text fields with a segmented control showing all the accepted unit options as selectable buttons.
For example:
- Power unit: [ W ] [ kW ] [ MW ]
- Hash rate unit: [ GH/s ] [ TH/s ] [ PH/s ]
This approach fits well here because the number of valid options per field is small and well-known, making a segmented control more immediate and readable than a dropdown. It also clearly communicates to the user that they are choosing a unit, not typing a value.
Activity
refactor(frontend): use shared config form for miner controllers (edg…
docs(changelog): add entries for config form layout and miner control…
feat(frontend): reorganize config forms and add unit segmented contro…
Merge pull request #38 from markoceri/fix/issue-17-18-config-forms