feat(junction): edit complex cutbacks and corners

This commit is contained in:
que01 committed 2026-09-08 14:30:43 +08:00
1 parent d0e1f62f2b
commit 80f122be46
15 files changed
+354 -38

No files matched your search

+7 -7
View File
@@ -281,15 +281,15 @@ reuse the unscoped singular structure when its ref differs. A missing structure
stays unavailable. Use `junctionEditSelection(ref)` for edit-state and preview
requests so a cluster never falls back to the last selected road or node.
## 17. Complex carriageway width editing
## 17. Complex geometry editing
Complex JunctionTools consumes the same v2 `EditSession`, `PreviewRequester`,
`ParameterPanel`, and map handle callbacks as ordinary junctions. The only
editable handle in this stage is `cluster-carriageway-width` with a
`cluster-carriageway` anchor. Before edit mode, a selected cluster loads its
scoped manifest so `canEditJunction()` can use an editable server handle as the
capability signal. Once enabled, those same handles are rendered on the map and
in the panel; `App.tsx` resolves the anchor snapshot from `sourceRoadIds[0]`.
`ParameterPanel`, and map handle callbacks as ordinary junctions. Editable
handles are `cluster-carriageway-width`, `cluster-carriageway-cutback`, and
`cluster-corner-radius`. The first two use a `cluster-carriageway` anchor; a
corner anchor is resolved to its representative carriageway only to create the
snapshot. Before edit mode, a selected cluster loads its scoped manifest so
`canEditJunction()` can use an editable server handle as the capability signal.
Do not add a cluster-local draft, preview, undo, or save flow.
Compiler structure provenance supplies cluster hotspots and external road IDs.