feat: complete complex junction transition editing
This commit is contained in:
1 parent
801d8be980
commit
79f83412e6
18 files changed
+400
-59
No files matched your search
@@ -318,3 +318,17 @@ Map capability reason codes into user-facing Chinese descriptions.
|
||||
Required checks: opposite node/cluster scopes with equal raw IDs, unknown scope,
|
||||
list-to-feature grouping and feature-to-list identity, foreign-cluster exclusion,
|
||||
raw signal UID selection, map identity preservation, and reload stability.
|
||||
|
||||
### Junction workspace save and grouped ranges
|
||||
|
||||
Workspace actions must include `EditSession.dirty`, `canUndo`, and `canRedo`;
|
||||
`JunctionSession.dirty` alone misses settled grouped edits. Reuse the global
|
||||
commands and expose save status in the junction route, where the main header is
|
||||
hidden. The edit render revision is not a persisted document version: a save
|
||||
changes it, so comparing a captured render revision after saving can crash React.
|
||||
The API owns version conflict checks.
|
||||
|
||||
A grouped scalar is available only if the individual ranges intersect. Otherwise
|
||||
show why a common value is unavailable and expand individual controls; never
|
||||
render a minimum larger than the maximum. Transition length uses the same input,
|
||||
preview, history, and persistence path as other geometry parameters.
|
||||
Reference in new issue
Block a user