refactor(workbench): split editor state and components

This commit is contained in:
que01 committed 2026-09-02 15:04:58 +08:00
1 parent caa3cb843f
commit 834470cfa1
23 files changed
+1219 -878

No files matched your search

@@ -14,6 +14,8 @@ The workbench frontend uses Prettier as the source formatting authority. Code is
- Do not commit dense, manually minified, or single-line JSX/TypeScript.
- Do not hand-format around Prettier output.
- Do not leave a page component responsible for unrelated form implementations, API calls, and multiple edit histories after a named component or hook boundary exists.
- Do not duplicate an edit protocol while extracting it. Move ownership and update call sites in one change so there is only one active path.
---
@@ -22,6 +24,8 @@ The workbench frontend uses Prettier as the source formatting authority. Code is
- Run `npm run format` after editing frontend files.
- Run `npm run format:check` in the validation gate.
- Keep React components, hooks, types, and API clients in separately formatted modules once a component becomes non-trivial.
- Keep `App.tsx` as a composition root. New domain behavior belongs in a hook or named component with typed props.
- Refactors must preserve API call order, DOM-visible labels/defaults, and OpenLayers map identity unless the task explicitly changes them.
---
@@ -35,3 +39,4 @@ The workbench frontend uses Prettier as the source formatting authority. Code is
- Formatting check passes.
- UI behavior changes do not rebuild the OpenLayers map unless the map lifecycle explicitly requires it.
- Verify ordinary v1 staged, v2 direct-edit, and traffic-signal draft flows independently; passing one flow does not prove the others survived extraction.