mikael-lovqvists-claude-agent/electronics-inventory
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

future-plans: clarify SI prefix vs unit distinction

Browse Source 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
mikael-lovqvists-claude-agent
2026-03-22 15:03:33 +00:00
parent 8cb1d11e40
commit a17bafb6d3
1 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
future-plans.md
View File

@@ -132,11 +132,17 @@ dimension (e.g. `temperature`, `resistance`, `frequency`, `voltage`). The dimens
defines the set of valid units and the conversion factors between them (°C, °K, °R, defines the set of valid units and the conversion factors between them (°C, °K, °R,
°F for temperature; Ω, kΩ, MΩ for resistance; etc.). °F for temperature; Ω, kΩ, MΩ for resistance; etc.).
SI prefixes (k, M, µ, n, p, etc.) are not separate units — they are a presentation
layer on top of a unit. `25kΩ` should be parsed as value `25000`, prefix `k`, unit
`Ω`, and stored as `{ value: 25000, unit: "Ω" }` (or in a canonical base unit).
The prefix is re-applied on display based on the magnitude. This keeps comparisons
and conversions clean without treating kΩ and MΩ as distinct unit types.
This would allow: This would allow:
- Entering values in any compatible unit and storing in a canonical unit internally - Entering values in any compatible unit and SI prefix, storing canonically
- Displaying in the user's preferred unit - Displaying in the user's preferred unit and auto-selecting an appropriate prefix
- Parametric search with cross-unit comparisons (e.g. `temp_range > 200K` matching - Parametric search with cross-unit and cross-prefix comparisons (e.g. `R < 10k`
a component with `temp_range = -73°C`) matching both `4k7Ω` and `0.001MΩ`)
- Catching unit mismatches at entry time - Catching unit mismatches at entry time
## PDF / files ## PDF / files