aff4df325d
- Remove async refresh_workspace_seeded_units from date change handlers - Date changes now only call on_form_change() (updates cost estimates, marks results stale) - Entry spot is derived only when user clicks Run button - Form remains responsive during configuration - No more API errors when changing dates while configuring other fields
20 lines
968 B
YAML
20 lines
968 B
YAML
id: BT-005
|
|
title: Defer Entry Spot Derivation to Backtest Run
|
|
status: done
|
|
priority: P1
|
|
effort: S
|
|
depends_on: []
|
|
tags: [backtesting, ux, performance]
|
|
summary: Only derive entry spot from historical data when user clicks Run, not on every form change.
|
|
acceptance_criteria:
|
|
- Entry spot is NOT fetched when user changes start/end dates.
|
|
- Entry spot is NOT fetched when user changes other form fields.
|
|
- Entry spot IS derived when user clicks the Run button.
|
|
- Form remains responsive during date/field changes (no API calls blocking).
|
|
- Clear loading indicator shows when entry spot is being fetched during run.
|
|
- Previous entry spot value is retained until new one is derived.
|
|
notes:
|
|
Removed async refresh_workspace_seeded_units from date change handlers.
|
|
Entry spot derivation now only happens inside run_read_only_scenario when
|
|
the user clicks Run. Form changes now call on_form_change() which only
|
|
updates cost estimates and marks results stale. |