PowerShell / PowerShell/vscode-powershell

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

Open
#1,149 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-IntelliSense Bug: PowerShell Core Issue-Bug Up for Grabs
Dominant language
TypeScript
Stars
1.9k
Forks
547
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the tab-completion behavior in the VS Code PowerShell extension with the reported [PSCustomO expression and the provided PowerShell version. Trace the extension's completion behavior and verify that the short type name remains usable in the reported object-construction example.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.