Christophe Vila
619277b0ee
Confirmed against Garmin Connect's own workout view: a lap whose IntensityType merely repeats the immediately preceding lap's (e.g. a second "cool-down" lap right after the first) means the recording continued past the end of that step, not that the workout prescribed a second target for it. Only the first lap of such a run keeps its target/HR fields; the continuation shows the actual trace with no expectation overlay. Doesn't affect normal interval structure, since Effort/Recovery always alternate and never appear back-to-back.
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.