PowerShell / PowerShell/vscode-powershell

no tab complete for predefined cmdlet param values

Open
#3,753 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-psEditor Issue-Enhancement
Dominant language
TypeScript
Stars
1.9k
Forks
547
PR merge metrics
No merged PRs in 30d

Description

Prerequisites
  • I have written a descriptive issue title.
  • I have searched all issues to ensure it has not already been reported.
  • I have read the troubleshooting guide.
  • I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
  • I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
Summary

no tab complete for predefined cmdlet param values
Compare to the ISE or a PS prompt, where it works correctly.

The VSC peoples said this is an issue with the PS extension.

PowerShell Version
Name                           Value
----                           -----
PSVersion                      5.1.19041.1320
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1320
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
Visual Studio Code Version
the instructional code doesn't work, so this is from VSC's About dlg:
Version: 1.63.2
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:40:02.816Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19044
Extension Version
the instructional code doesn't work, so this is from the extension details page:
v2021.12.0
Last updated
12/22/2021, 15:56:27
Identifier
ms-vscode.powershell
Steps to Reproduce
  1. start a new PowerShell file
  2. type a cmdlet (e.g. 'get-item'), space, -err, tab <<-- this gives you "-ErrorAction"
  3. space
  4. tab, the predefined list of values (e.g., "Continue", "Ignore") does not appear
    THUS, you have to guess what the possible values are.
    Compare to the ISE or a PS prompt, where it works correctly.
Visuals

No response

Logs

No response

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 reported completion behavior in a new PowerShell file with get-item -err, then press Tab after entering the parameter value position. Trace the extension's completion handling from that reproduction; done means predefined values such as Continue and Ignore appear, matching the PowerShell prompt or ISE.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, typescript, vscode
Domain
devtools, 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.