Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose string-content #124

Merged
merged 3 commits into from
Jul 29, 2024
Merged

Expose string-content #124

merged 3 commits into from
Jul 29, 2024

Conversation

afroozeh
Copy link
Contributor

@afroozeh afroozeh commented Jun 5, 2024

Expose string_content to the parse tree so that we don't need to manually strip quotes to get the string content.

@github-actions github-actions bot added the grammar Related to the grammar label Jun 5, 2024
@fwcd fwcd merged commit 8cf7f01 into fwcd:main Jul 29, 2024
1 check passed
@fwcd
Copy link
Owner

fwcd commented Jul 29, 2024

Thanks! I regenerated the parser locally to resolve the conflict. The tree-sitter-cli is also updated to 0.22.6 now, which at least for me now deterministically generates the same parser on arm64 macOS as on x86_64 Linux in CI, so you should be able to just do npm run generate on your local machine in the future.

@afroozeh
Copy link
Contributor Author

@fwcd Thank you! I'll submit other PRs one-by-one!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
grammar Related to the grammar
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants