Tab complete for [PSCustomObject] tab completes [System.Management.Automation.PSCustomObject]

[JamesLear92]

System Details

• Operating system name and version: Windows 10 Enterprise
• VS Code version: 1.19.1
• Shell: 1.79
• Output from $PSVersionTable:
  Name Value

---

PSVersion 5.1.15063.726
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.15063.726
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

$pseditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
1      5      1      0

code --list-extensions --show-versions
GrapeCity.gc-excelviewer@2.0.16
ms-vscode.PowerShell@1.5.1

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.15063.726
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.15063.726
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

### Issue Description

Tab complete for [PSCustomO tab completes [System.Management.Automation.PSCustomObject]. This is a problem because [System.Management.Automation.PSCustomObject] cannot be used like:

[PSCustomObject]@{'Property' = $value}

### Attached Logs

[TylerLeonhardt]

Hey there, thanks for this report! We'll take a look 👍

[SeeminglyScience]

This is an issue with command completion provided by PowerShell and occurs outside of VSCode in Windows PowerShell. This was resolved in PowerShell Core.

That said, it would probably be worth looking into replacing the result we get from TabExpansion2 to fix this for those still on 5.1. It's unreasonably frustrating if you use the PSCustomObject type accelerator frequently. Edit 03/17/2020: Bad idea to replace completion text for 5.1. (Good idea to special case the tool tip in newer versions though)

[SydneyhSmith]

In PowerShell:

$script = "[pscustom"
$results = TabExpansion2 -inputScript $script -cursorColumn $script.Length
$results.CompletionMatches
CompletionText ListItemText ResultType ToolTip
-------------- ------------ ---------- -------
pscustomobject PSObject           Type Class System.Management.Automation.PSObject

So this behavior is not ideal...I will mark it as a PowerShell bug but will leave it open as up for grabs because we could special case this.