-
Notifications
You must be signed in to change notification settings - Fork 33
fix(ruby): adjust operator highlights #338
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
Open
AlternateRT
wants to merge
7
commits into
zed-extensions:main
Choose a base branch
from
AlternateRT:adjust-operator-highlights
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+59
−63
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
af609ad
fix(ruby): adjust operator highlights
AlternateRT c11450c
Fully scope `|` token captures
AlternateRT 9311224
Limit operator capture for `.` and `::` as well
AlternateRT de5d3f5
Fully scope conditional operator captures
AlternateRT ea5afc7
Fully scope `->`, `<<`, and `<` token captures
AlternateRT c2f3673
Adjust `hash_splat_nil` capture
AlternateRT 864b768
Fully scope `:` token captures
AlternateRT File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thought: Not sure that just removing operators here is a good idea. For example, removing the bare
-capture loses highlighting during parser recovery:TS places the operator call in an
ERRORrecovery node (and this is the upstream issue). That node has no usableoperator:field for-.I'd rather scope down operators first with overrides. We can check what Helix does.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has this been reported to upstream? I don't think we should concern ourself with what is a parsing error of the grammar.
After all, that example you gave should be valid code.
Helix seems to avoid bare captures for operators as much as possible too: https://github.com/helix-editor/helix/blob/master/runtime/queries/ruby/highlights.scm#L1-L21