Extract dataset workflow orchestration
This commit is contained in:
@@ -7,6 +7,13 @@
|
||||
|
||||
# Changelog
|
||||
|
||||
## Sprint 28 dataset workflow hook hardening (2026-06-17)
|
||||
|
||||
- Moved dataset selection, upload, detail loading, dataset jobs and raster/vector operation orchestration from `App.tsx` into `useDatasetWorkflow`.
|
||||
- Kept project dataset listing in `App.tsx` so project/area loading remains the shared workbench boundary.
|
||||
- Added regression coverage to verify `App.tsx` still wires dataset, raster and vector UI callbacks while operation API ownership stays inside the focused hook.
|
||||
- No API contracts, backend behavior, migrations, product features, provider fetching, AI behavior or UI redesign were introduced.
|
||||
|
||||
## Sprint 27 export and QA workflow hook hardening (2026-06-17)
|
||||
|
||||
- Moved Export Center orchestration state and API calls from `App.tsx` into `useExportWorkflow`.
|
||||
|
||||
Reference in New Issue
Block a user