You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is in the same boat as issue #379 I logged. If I use a scope modifier (like $Script:) in front of a variable Go To Definition cannot find the definition. Similarly Find All References will only find all references that use the modifier and not the initial declaration at the script level. This one could be tricky to implement because variables set in a function with the same name as a script level variable are created at the Local scope.
The text was updated successfully, but these errors were encountered:
Yep, we haven't done the necessary work to make all of our language featues scope-aware. This is being tracked here: PowerShell/PowerShellEditorServices#16. We'll be starting on this work within the next couple of months.
Please fill in these details so that we can help you!
System Details
$PSVersionTable
:PSVersion 5.0.10240.17146
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.42000
BuildVersion 10.0.10011.16384
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3
Issue Description
This is in the same boat as issue #379 I logged. If I use a scope modifier (like $Script:) in front of a variable Go To Definition cannot find the definition. Similarly Find All References will only find all references that use the modifier and not the initial declaration at the script level. This one could be tricky to implement because variables set in a function with the same name as a script level variable are created at the Local scope.
The text was updated successfully, but these errors were encountered: