-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
Ensure find-all-refs works on unresolved locals #38836
Labels
Domain: Symbol Navigation
Relates to go-to-definition, find-all-references, highlighting/occurrences.
Experimentation Needed
Someone needs to try this out to see what happens
In Discussion
Not yet reached consensus
Rescheduled
This issue was previously scheduled to an earlier milestone
Suggestion
An idea for TypeScript
Milestone
Comments
DanielRosenwasser
added
Suggestion
An idea for TypeScript
In Discussion
Not yet reached consensus
Domain: Symbol Navigation
Relates to go-to-definition, find-all-references, highlighting/occurrences.
labels
May 28, 2020
This was referenced Jun 12, 2020
Another option is to use results of navTo when symbol is not resolved instead of changing symbol tables? |
RyanCavanaugh
added
the
Rescheduled
This issue was previously scheduled to an earlier milestone
label
Aug 31, 2020
DanielRosenwasser
added
the
Experimentation Needed
Someone needs to try this out to see what happens
label
Sep 15, 2021
This was referenced Sep 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Domain: Symbol Navigation
Relates to go-to-definition, find-all-references, highlighting/occurrences.
Experimentation Needed
Someone needs to try this out to see what happens
In Discussion
Not yet reached consensus
Rescheduled
This issue was previously scheduled to an earlier milestone
Suggestion
An idea for TypeScript
Spoke with @amcasey about this one.
Given the following
blah
will be an unresolved and should be an error, but we still want find-all-references on this symbol to work reasonably well. This is especially important in the mode described in #37713, where TypeScript won't have access to symbols in the global scope.This can potentially be achieved by creating an "error scope" whose symbol table contents are progressively populated every time resolution fails.
The text was updated successfully, but these errors were encountered: