Christophe Vila
a6efcec33b
Y-axis ticks now use a fixed small count (3) snapped to round increments (30s for pace, 5-20bpm for HR depending on range) instead of Recharts' automatic placement, which was silently dropping most ticks in the ~100px-tall mini chart and occasionally leaving only one label visible. A light vertical line now marks every point the effort type changes, even between phases that don't get a background color. Warm-up and cool-down segments -- which rarely have a target band -- get a dashed line at their own average pace/HR instead, as a reference point. "Pertuis - 1500m Hill" showed no phase coloring because its lap uses Garmin's INTERVAL intensity type, which wasn't mapped -- confirmed via query that 23 laps across the account use it, alongside the 5 types already handled. It's the same concept as ACTIVE (a work/effort segment), so it now shares that color and label.
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some Oxlint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Oxc
- @vitejs/plugin-react-swc uses SWC
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the Oxlint configuration
If you are developing a production application, we recommend enabling type-aware lint rules by installing oxlint-tsgolint and editing .oxlintrc.json:
{
"$schema": "./node_modules/oxlint/configuration_schema.json",
"plugins": ["react", "typescript", "oxc"],
"options": {
"typeAware": true
},
"rules": {
"react/rules-of-hooks": "error",
"react/only-export-components": ["warn", { "allowConstantExport": true }]
}
}
See the Oxlint rules documentation for the full list of rules and categories.