Extract dataset workflow orchestration
This commit is contained in:
@@ -184,6 +184,12 @@ React + TypeScript + MapLibre foundation for project/area/dataset workflow.
|
||||
- Detection and segmentation QA continue to share the same persisted QA/QC refresh path through `loadQualityChecks`.
|
||||
- Export Center and QA/QC UI behavior is unchanged; `App.tsx` still coordinates selected project, dataset and analysis-run state.
|
||||
|
||||
## Sprint 28 maintainability updates
|
||||
|
||||
- Dataset selection, upload form state, detail loading, dataset jobs and raster/vector operation orchestration moved from `src/App.tsx` into `src/hooks/useDatasetWorkflow.ts`.
|
||||
- Project-scoped dataset listing remains in `App.tsx` because it is still part of the shared project/area load boundary.
|
||||
- Dataset details, raster controls, vector controls and job list behavior are unchanged; the UI still receives the same callbacks and state.
|
||||
|
||||
## Release hardening updates
|
||||
|
||||
- Production builds split application code, React vendor code and MapLibre vendor code into separate chunks.
|
||||
|
||||
Reference in New Issue
Block a user