fd6efe2c7e
Clubs that reconfigure their track (e.g. running indoors in the same building) can now add named track layouts under Settings, each with just a start date/time - layouts are contiguous, so a layout's end is implicitly the next one's start, with no separate field to keep in sync. Every session freezes which layout was active when it started, so the "track record" audio cue and the Results Archive (which now shows each session's layout) only compare laps run on the same physical track. With no layouts configured, everything behaves exactly as before - the feature is fully inert until a club uses it. Design settled through conversation with the user: global scope (not per class), start-date-only (no redundant stop date), and no changes needed to driver/transponder mapping, since that's already fully independent of track geometry in this app. Deliberately out of scope for this pass: the mobile/driver training profile's own cross-session personal-best trend stats still compare across a driver's whole lap ledger regardless of layout - logged in ROADMAP.md as a real remaining gap for a later pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
22 lines
705 B
JavaScript
22 lines
705 B
JavaScript
import "./training_logic.test.js";
|
|
import "./public_training_profile.test.js";
|
|
import "./race_timing_logic.test.js";
|
|
import "./track_layouts_logic.test.js";
|
|
import "./race_day_logic.test.js";
|
|
import "./backup_service.test.js";
|
|
import "./judging_logic.test.js";
|
|
import "./runtime_persistence.test.js";
|
|
import "./audio_runtime.test.js";
|
|
import "./race_audio.test.js";
|
|
import "./decoder_runtime.test.js";
|
|
import "./csv_import.test.js";
|
|
import "./server_persistence.integration.test.js";
|
|
|
|
import "./training_views.test.js";
|
|
|
|
import "./session_replay.test.js";
|
|
import "./public_training_refresh.test.js";
|
|
import "./list_sorting.test.js";
|
|
import "./sync_status.test.js";
|
|
import "./decoder_diagnostics.test.js";
|