Skip to content

Resolve various (engine) hours issues#27

Merged
hawkinslabdev merged 2 commits into
mainfrom
issues/odometer-workflow
May 6, 2026
Merged

Resolve various (engine) hours issues#27
hawkinslabdev merged 2 commits into
mainfrom
issues/odometer-workflow

Conversation

@hawkinslabdev
Copy link
Copy Markdown
Owner

I found issues where the code assumed all trackers used distance, breaking things for hours-based ones. This PR will add guards, triggers, and messages to handle both distance and hours properly, and patched old data to match.

- use static JSON imports for locale files to ensure production availability
- fallback to first notes line as title for orphaned service logs
- reorder PDF entry structure: bold title first, then meta
- add cost display to PDF entries with locale-aware formatting
- initialize `next_due_measurement` for hours trackers
- remove distance-only guards in tracker status computation
- remove hardcoded basis from odometer triggers
- set unit-aware DUE_SOON window (1h for hours, 50km for distance)
- use vehicle odometer unit in warning messages
- patch existing trackers with null `next_due_measurement`
@hawkinslabdev hawkinslabdev self-assigned this May 6, 2026
@hawkinslabdev hawkinslabdev merged commit 86017df into main May 6, 2026
1 check passed
@hawkinslabdev hawkinslabdev deleted the issues/odometer-workflow branch May 6, 2026 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant