fix: link @lsp.type.variable to @variable#237
Merged
Conversation
s-cerevisiae
force-pushed
the
push-zlkrlxsrxutx
branch
from
8cb199b to
9a7ad9e
Compare
s-cerevisiae
force-pushed
the
push-zlkrlxsrxutx
branch
from
9a7ad9e to
a26f0d9
Compare
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
2 participants
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.
I'm not sure if it was intentional but the highlight of
@lsp.type.variablewas cleared. This doesn't make too much difference with tree-sitter enabled except when the variable is inside a format string:This PR fixes the issue by linking it to
@variableagain: