bu5hm4nn/vault-dash
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: defer entry spot derivation to backtest run (BT-005)

Browse Source 
- 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
This commit is contained in:
Bu5hm4nn
2026-04-06 11:14:51 +02:00
parent 4af7a09c6e
commit aff4df325d
3 changed files with 12 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/roadmap/done/BT-005-defer-entry-spot-derivation.yaml Normal file
View File

@@ -0,0 +1,20 @@
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.