Releases: AmetAlvirde/normalize-fit-file
Release list
v1.5.0
v1.5.0
- Introduces a shared internal option-spec parser used by all CLI subcommands.
Changed
- Refactored
parse-ffp,parse-garmin, andcompareargument parsing to remove duplicated format/output/default-path logic. - No CLI flags, default output paths, or public library exports changed.
What's Changed
- Adds typed internal report, label boundary, and compare module split by @AmetAlvirde in #8
- Adds parser refactor by @AmetAlvirde in #12
Full Changelog: v1.4.0...v1.5.0
v1.4.0
Compare uses an internal typed report (a / b) and a single label boundary before write; CLI split into report / labels / render. No intentional behavior change for CLI users or report JSON/YAML consumers.
Full Changelog: v1.3.0...v1.4.0
v1.3.0
Internal vendor adapter seam so FIT-from-FFP and FIT-from-Garmin both use the same extract → assemble pipeline, with per-adapter row passes (FFP keeps its rename passes; Garmin uses an empty pass list). Normalized output and the public package surface stay the same—new Extracted / Pass pieces are internal only, not exported.
Why it matters: Less duplicated assembly logic, easier to add another parser later without drifting behavior, and clearer structure in parse-ffp / parse-garmin.
Also: Process/context and ADR documentation for this decision (e.g. vendor adapter ADR in the repo).
What's Changed
- Ads vendor seam by @AmetAlvirde in #4
Full Changelog: v1.2.0...v1.3.0