SEV-362: format v0.2.0 — boundary spacing, acronyms, formatRange, numeric budget #2
Reference in New Issue
Block a user
Delete Branch "sev-362/format-v0.2.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hardens the shared formatters ahead of all three frontends finally consuming this package (fixes "NaN miles", "Range: 100 150mi", "Level2"):
formatLabel: letter→digit boundary spacing ("level2" → "Level 2"), acronym casing (DCFC/EV/SUV/VIN/DC/A/C), bare numeric ranges pass through untouchedformatRange: "150-200" → "150–200 mi", "200+" → "200+ mi"; empty → '' (callers render "Not specified")formatBudgetis now the numeric (min, max) dollar formatter matching the API payload; the wizard's slug map moves toformatBudgetBucketvehicleName({year, make, model, commissioned})Breaking rename is safe — nothing consumes 0.1.0. Publish to the Gitea registry follows merge.
🤖 Generated with Claude Code
- formatLabel: letter→digit boundary spacing ("level2" → "Level 2"), acronym casing (DCFC/EV/SUV/VIN/DC/A\C), bare numeric ranges pass through untouched - new formatRange: "150-200" → "150–200 mi", "200-plus"/"200+" → "200+ mi"; empty → '' (callers render their own placeholder) - formatBudget is now the numeric (min, max) dollar formatter matching the API payload; the wizard's slug map moves to formatBudgetBucket - new vehicleName({year, make, model, commissioned}) Breaking rename of formatBudget is safe: no frontend consumes 0.1.0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>