Replay pending changes in one private document draft
This commit is contained in:
@@ -897,3 +897,14 @@ The application's initial loading fit targets the current canvas's direct node
|
||||
members, including partition entries. Expanded descendant cards remain rendered
|
||||
and pannable but cannot move their parent entry outside the initial viewport.
|
||||
The manual fit control keeps its existing whole-scene behavior.
|
||||
|
||||
Pending-operation reconciliation replays ordered change batches in one private
|
||||
core draft. Each change still sees the results of earlier changes: field presence,
|
||||
incarnation, before-value conditions and current owner scope are checked in that
|
||||
order. Already-satisfied changes are skipped, but field scope is checked first.
|
||||
Only the final document envelope escapes; a late conflict discards the draft and
|
||||
leaves the input ACK and ledger unchanged. The runtime retains sequence sorting,
|
||||
operation/history-effect admission and final registry/topology validation. This
|
||||
removes a full table copy for every pending change without adding intermediate
|
||||
Roots, history units or network writes. `applyChanges` uses the same conditional
|
||||
change application path and retains its existing strict/default behavior.
|
||||
|
||||
Reference in New Issue
Block a user