Use tree-sitter-ruby for crystal #5205
Merged
Conversation
This file contains 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
the-mikedavis
added
C-bug
kirawi
pushed a commit
to kirawi/helix
that referenced
this pull request
Jan 25, 2023
freqmod
pushed a commit
to freqmod/helix
that referenced
this pull request
Feb 8, 2023
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.
tree-sitter-crystal has some parse failures that make it very likely to have bad highlights on regular files (for example https://github.com/Blacksmoke16/oq/blob/master/src/oq.cr). It looks like there are some parse failures for strings in particular that lead to the file mostly being highlighted as a string.
Crystal and Ruby and close enough syntax-wise that we can probably get away with using tree-sitter-ruby until tree-sitter-crystal matures.