The map had one input device. A drag projects a pointer onto the manifest's axis; there was no way to state a value, read one, or withdraw one. Both channels now meet at the same three exits in App.tsx — draftValue() previews, settleValue() commits one undoable command, abandonGesture() puts the settled state back — so nothing about the constraint, the debounce or the previewSeq arbitration is implemented twice. EditSession is untouched: focus and blur land on the gesture boundary that pointerdown and pointerup already used, which is why typing 1.53 is one undo step rather than four. Three rules the two devices do not share: - Live drag values bypass React and write the input's value directly, per direct-edit-client.md §7. A layout effect re-applies them after a mid-drag preview replaces the manifest, and drops the override once the manifest reports the value the drag asked for. - Typed values out of range are refused, not clamped. A pointer cannot state an intent it never reached, so a drag clamps; typed text is an intent, and a clamped typo reads as a plausible value that can go unnoticed. The offered extremes round inward — a real max of 2.925 renders as 2.93 under nearest-rounding, which the range it came from would then reject. - Reset disables the constraint rather than deleting it: validateEditDocument() rejects an operation naming a constraint that is not in the document. This is the one edit a drag cannot express, since a drag can set a value but never withdraw one. Interval editing stays behind intervalEditingSupported, which is still false — compileGeometry() does not read profile.interval, and a control that changes nothing is worse than no control. The conversions are implemented and tested so the row appears when the flag flips. Probing a live manifest turned up a defect that is not from this change and is not fixed here: an edge offset advertises ±2.925 while the solver rejects past about ±1. Evidence is in the task's research/, and the requirement moved to 08-31-constraint-range-validation. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
51 lines
1.6 KiB
JSON
51 lines
1.6 KiB
JSON
{
|
|
"id": "direct-manipulation-road-editor",
|
|
"name": "direct-manipulation-road-editor",
|
|
"title": "直接操纵道路编辑工作台",
|
|
"description": "探索类似 Drawtonomy 的直接操纵道路编辑,保持结构化 overrides、可审计性和可重编译性",
|
|
"status": "planning",
|
|
"dev_type": "feature",
|
|
"scope": "road-editor",
|
|
"package": null,
|
|
"priority": "P2",
|
|
"creator": "dingkang",
|
|
"assignee": "dingkang",
|
|
"createdAt": "2026-08-26",
|
|
"completedAt": null,
|
|
"branch": null,
|
|
"base_branch": "main",
|
|
"worktree_path": null,
|
|
"commit": null,
|
|
"pr_url": null,
|
|
"subtasks": [],
|
|
"children": [
|
|
"08-26-direct-edit-documents",
|
|
"08-26-direct-edit-solver-api",
|
|
"08-26-direct-edit-map-editor",
|
|
"08-26-direct-edit-junction-tools",
|
|
"08-27-junction-dominated-roads",
|
|
"08-28-edit-interaction-polish",
|
|
"08-28-junction-control-offsets",
|
|
"08-28-crosswalk-element-editor",
|
|
"08-31-parameter-panel-binding",
|
|
"08-31-constraint-range-validation"
|
|
],
|
|
"parent": null,
|
|
"relatedFiles": [
|
|
"src/compile/compiler.js",
|
|
"src/compile/native-road.js",
|
|
"src/compile/complex-junction.js",
|
|
"src/compile/layer-manifest.js",
|
|
"src/geometry/lane-geometry.js",
|
|
"workbench/server.js",
|
|
"workbench/client/src/App.tsx",
|
|
"workbench/client/src/components/MapCanvas.tsx",
|
|
"workbench/client/src/map/layers.ts",
|
|
"workbench/client/src/lib/api.ts",
|
|
"workbench/client/src/types/state.ts",
|
|
"test/index.js",
|
|
"test/fixtures.js"
|
|
],
|
|
"notes": "父任务:持有需求集、design.md 权威合约、跨子任务验收与第 8 步集成验证。实现落在三个子任务。",
|
|
"meta": {}
|
|
} |