Repository navigation
fix: set parents for all variadic inserted nodes - #343
Open
feritcemkahraman wants to merge 1 commit into
Open
feritcemkahraman wants to merge 1 commit into
feritcemkahraman wants to merge 1 commit 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
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.
When
insertBeforeorinsertAfterreceives multiple new nodes, only the first node gets a parent. Later nodes are serialized but theirremove()call does nothing, and sibling navigation cannot resolve the container.Assign the parent to each additional node. Add regressions for both insertion methods that verify the parent and subsequent removal.
Validation: both new tests fail before the fix; all 798 tests pass after it. Build, TypeScript checks, and lint pass (lint reports two existing warnings in exceptions.mjs).