Repository navigation
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.
Building
{ item: ["first", null, "last"] }currently emits the empty node beforefirst, changing the array's order. Repeated processing instructions have the same problem.Append null entries to the repeated-node buffer in place. The existing
oneListGrouprepresentation is preserved.Validation: five new regressions fail on the base revision; all seven focused cases and the complete suite pass (143 specs, 0 failures, 1 existing pending). Both bundles build, ESM/CommonJS runtime checks pass, and the new spec passes ESLint.
Direct source lint has the same four existing errors as the base. The current lint script references an absent
benchmarkdirectory, andtest-typesreferences an absentspec/typings/typings-test.ts.