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

future-plans: measurement dimensions and unit conversion

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:02:32 +00:00
parent 98190c5271
commit 8cb1d11e40
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
future-plans.md
View File

@@ -126,6 +126,19 @@ Currently all field values are free-text strings. Typed fields (numeric,
enum/dropdown) would enable better formatting, validation, and range-aware search. enum/dropdown) would enable better formatting, validation, and range-aware search.
Prerequisite for parametric search with range operators. Prerequisite for parametric search with range operators.
#### Measurement dimensions and unit conversion
Instead of a bare unit string on a field, associate a field with a measurement
dimension (e.g. `temperature`, `resistance`, `frequency`, `voltage`). The dimension
defines the set of valid units and the conversion factors between them (°C, °K, °R,
°F for temperature; Ω, kΩ, MΩ for resistance; etc.).
This would allow:
- Entering values in any compatible unit and storing in a canonical unit internally
- Displaying in the user's preferred unit
- Parametric search with cross-unit comparisons (e.g. `temp_range > 200K` matching
a component with `temp_range = -73°C`)
- Catching unit mismatches at entry time
## PDF / files ## PDF / files
### File picker search filter ### File picker search filter