feat(yaml_parser): parse block sequence #6727
Merged
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
|
CodSpeed Performance ReportMerging #6727 will not alter performanceComparing Summary
|
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.
Summary
Parse YAML block sequence in the form of
This PR also changes the lexer's tokens emit order, now all
*_ENDtokens must be followed by at least one NEWLINE token. This will disallow these tokens from being attached trailing tokens, as the trailing tokens attaching logic doesn't work properly with zero-width token like theseCompact forms of block sequences and mappings are also removed in this PR, as they now longer needed to be explicitly handled by the parser.
Test Plan
Added new tests for in form of YAML files containing both YAML block sequences and block mapping.