docs: explain two-phase flow-sequence handling in sync()#53
Open
nathanjmcdougall wants to merge 2 commits into
Open
docs: explain two-phase flow-sequence handling in sync()#53nathanjmcdougall wants to merge 2 commits into
nathanjmcdougall wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the proactive/reactive split in
Document.sync()that was previously unexplained.Phase 1 (
_flow_seq_replacements) pre-converts only the affected flow sequences so that nested list indentation is preserved. A full replace at a higher path would re-serialise the whole mapping with 2-space indentation.Phase 2 (the
except PatchErrorfallback) catches cases phase 1 misses — primarily list reordering, where new diff indices weren't in the original tree.