Add export history controls
This commit is contained in:
@@ -2240,3 +2240,30 @@ Limitations:
|
||||
|
||||
Next recommended pass:
|
||||
- Continue with export history filtering or retention controls if repeated demo runs keep growing artifact history.
|
||||
|
||||
## Sprint 56 export history controls (2026-06-17)
|
||||
|
||||
Changed:
|
||||
- Added frontend-only search for export type, status, id and storage path in the Exports workspace.
|
||||
- Added export type and status filters generated from the loaded export records.
|
||||
- Made the latest-10 limiter apply after filtering so large histories stay manageable without hiding matching records unexpectedly.
|
||||
- Added a clear no-match empty state and reset view action.
|
||||
- Slightly compacted export action buttons so the history controls are visible earlier on standard desktop viewports.
|
||||
- Added regression coverage for the export history controls, filtered list limiting and no-match state.
|
||||
|
||||
Tested:
|
||||
- `cd frontend && npm run typecheck`
|
||||
- `cd backend && python -m pytest tests/test_sprint51_quality_export_polish.py -q`
|
||||
- `cd frontend && npm run build`
|
||||
- Local Browser visual audit against `http://127.0.0.1:5178` using the live Tower API proxy.
|
||||
- Verified Exports history controls render with 50 live artifacts and a `report` search narrows the list to 17 matching artifacts.
|
||||
- Browser console error/warning check returned no entries.
|
||||
|
||||
Open:
|
||||
- Run full readiness, deploy Tower and verify the live Exports filters on `http://192.168.10.150:1202`.
|
||||
|
||||
Limitations:
|
||||
- This pass remains frontend UI hardening only. It does not add backend filtering, retention deletion, API changes, migrations, live provider fetching or AI model behavior.
|
||||
|
||||
Next recommended pass:
|
||||
- Consider a safe export retention/cleanup command if the artifact table keeps growing beyond demo needs.
|
||||
|
||||
Reference in New Issue
Block a user