-
Notifications
You must be signed in to change notification settings - Fork 227
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
Fix finding variable definitions in workspace #458
Conversation
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.
Looks good! I wonder if there's any special consideration we need to take for $module:
-scope variables?
@@ -14,25 +14,31 @@ namespace Microsoft.PowerShell.EditorServices | |||
internal class FindDeclartionVisitor : AstVisitor |
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.
Mind fixing the typo in the name of this class? FindDeclarationVisitor. That's bugged me for a while :)
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.
fixed!
To take
The advantage with 2 is that we will have a robust solution and the techniques used there can then also be used in rename logic. |
I'm all for using the existing variable analysis logic, maybe it's better to wait to do that until we can centralize our analysis and workspace logic in a reusable module |
The existing variable analysis logic is still somewhat buggy and needs some work. But I agree that we should centralize our analysis logic then use it from there. |
Thanks dude! Feel free to merge it once the tests pass |
First phase of streamlined development setup
Resolves PowerShell/vscode-powershell#710