Fix "Go to Definition" for variables used in list comprehensions(LSP highlighting not working for variables defined in list comprehension #2549)#2597
Open
pswitchy wants to merge 2 commits intofacebook:mainfrom
Conversation
|
@yangdanny97 has imported this pull request. If you are a Meta employee, you can view this in D95438997. |
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.
Motivation:
Currently, when you are working with a list comprehension like
[x for x in items], the "Go to Definition" feature works for the variable after the for (the targetx), but it fails and returns nothing if you try it on the variable before the for (the usagex).This PR fixes that bug so that clicking on the usage
xwill correctly take you to where it is defined.Approach:
The bug happens because of how the Pyrefly language server tries to follow the chain of variable references.
IterableValue.IterableValuestep, so it would give up and return nothing.IterableValueas a valid stopping point. Now, when the search hits this point, it correctly returns the location of the variable.Tests:
Tests Screenshots

