VSCode Peek / Go to Definition functions do not work when variable is cast as specific type

[stukey]

System Details

• Operating system name and version: Windows 10
• VS Code version: 1.25.1
• PowerShell extension version: 1.8.1
• Output from $PSVersionTable: see below

S C:\Users\me> code -v
1.25.1
1dfc5e557209371715f655691b1235b6b26a06be
x64
PS C:\Users\me> $psEditor.EditorServicesVersion
 
Major  Minor  Build  Revision
-----  -----  -----  --------
1      8      1      0
 
PS C:\Users\me> code --list-extensions --show-versions
[email protected]
[email protected]
[email protected]
 
PS C:\Users\me> $psversiontable
 
Name                           Value
----                           -----
PSVersion                      5.1.14393.2248
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.2248
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

I am not sure whether this is a VSCode issue or a PowerShell Extension issue so please forgive me if I have logged this in the wrong place.

In the latest version of VSCode (1.25.1) with the latest version of the PowerShell Extension (1.8.1) on Windows 10:

If you cast your variables by prefixing them with the type, e.g. [string], the “Go to Definition” and “Peak Definition” functions do not work.

Example:
 
[string]$testVar = "Test123"
 
$testVar

Right-click on the second ‘$testVar’ and select either “Go to Definition” or “Peak definition” and you’ll get an error “No definition found for $testVar”. Screenshot:

Try it without casting it as a [string] and it works as expected.

[TylerLeonhardt]

I have a fix for this - plus some bonus fixes :)

[stukey]

@tylerl0706 Great news. Thanks Tyler. Any more info on the bonus fixes 👍

[TylerLeonhardt]

$var1 = "string"
$var1

[string] $var2 = "string"
$var2

[NotNull()] $var3 = "string"
$var3

$a, $var4 = "string", "sss"
$var4

$a, [string] $var5 = "string", "sss"
$var5

will all go to the correct spot.

[mklement0]

@stukey: Just to aid in discovery of this issue, can you please correct the typo in the title (and body)? peak -> peek

[stukey]

Sure if you can tell me how to do that. I can’t see an option to edit the title, only the body of the original post.

[stukey]

Ah looks like @tyler0706 already did it.

[mklement0]

@stukey: Great; in general, look for the button labeled Edit to the right of the title:

[stukey]

Yup 🤯 I did edit the post but didn’t see any option to edit the title. Maybe it’s because Im getting the mobile view on my iPhone.

…

On 24 Jul 2018, at 18:07, Michael Klement ***@***.***> wrote: @stukey: Great; in general, look for the button labeled Edit to the right of the title: — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[TylerLeonhardt]

👍