-
Notifications
You must be signed in to change notification settings - Fork 223
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
Account for function and variable scope in language service features #16
Labels
Comments
This requires similar logic to #28 so potentially both could be developed at the same time. |
daviwil
changed the title
Use correct scope on variables and parameters for intellisense features
Consider variable scope for language intelligence features
May 18, 2016
daviwil
changed the title
Consider variable scope for language intelligence features
Account for function and variable scope in language intelligence features
May 18, 2016
daviwil
changed the title
Account for function and variable scope in language intelligence features
Account for function and variable scope in language service features
May 18, 2016
TylerLeonhardt
added
Area-Code Navigation
Area-IntelliSense
and removed
Up for Grabs
Will shepherd PRs.
labels
Jan 17, 2018
TylerLeonhardt
pushed a commit
to TylerLeonhardt/PowerShellEditorServices
that referenced
this issue
Jul 16, 2019
…esymbolshandler A working WorkspaceSymbolsHandler
Adding an example of this: function myDemo ($o) {
$o = "second"
}
$o = "first"
$o # Go to definition here will go to first match -> reassignment on line 2 Update: Preview extension v2023.2.0 includes change from #1984 which now shows all definitions. Good enough? Matching scope is hard, so not sure if/when that will be fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the following intellisense features the entire file (or multiple files if dot sourced) is/are being searched through for variable and parameters:
We need fix this to use the correct scope when searching on variables and parameters.
The text was updated successfully, but these errors were encountered: