feat(parser): allow dictionary entries without parentheses - #161
Merged
Merged
Conversation
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 16, 2026
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.
Dictionary literals now accept unparenthesized entries such as
!{"BE" => 100, "FR" => 80}alongside existing parenthesized pairs. Both forms bind as orderedPairLiteralSyntaxentries, with each entry's authored text and span preserved. Standalone pairs still require parentheses.The Tree-sitter grammar and generated parser were updated, with corpus and .NET syntax-binding coverage for shorthand, mixed styles, function arguments, source preservation, and malformed entries.
Validation:
npm run generate; dictionary corpus 5/5; applicable Tree-sitter corpus 377/377 (six existing Windows newline snapshot mismatches excluded);dotnet test Expressif.Syntax.sln --no-restore --nologo496/496 on net8.0, net9.0, and net10.0.Closes #160