Open JustinWebDev opened 2 years ago
thanks @JustinWebDev for your issue! Does this reproduce in both the PowerShell file editor as well in the integrated console? It would also be great to know if this reproduces for you in our preview extension? Thanks so much!
Sydney, it works correctly in the integrated console.
I know the VS code team said it was an extension issue, but IMO it's more of a VS code issue. Tab in VS code will insert whitespace unless you have the intellisense menu open. There is a tab completion option, but if you enable that it only tab completes if you are at the edge of a word, not in the middle of whitespaces.
The only thing the extension can do is to add space as an intellisense trigger character here: https://github.com/PowerShell/PowerShellEditorServices/blob/master/src/PowerShellEditorServices/Services/TextDocument/Handlers/CompletionHandler.cs#L56 this would cause the intellisense menu to pop up and let you tab complete the options, but you won't be able to tab complete without that menu open unless some changes are made on the VS code side.
Adding space as a trigger character could get annoying without some additional intelligence to only do it after parameters, preferably only parameters with a real form of tab completion (ValidateSet, Enums, Registered argument completer).
As a workaround, you as a user can get into the habit of using colons instead of whitespace to define parameter values like this: dir C:\ -ErrorAction:Stop
. Colons will act both as an intellisense trigger character, and allow you to be close to a word so the tab completion works.
FWIW you can hit ctrl-space to get the possible values, and then if your editor.tabCompletion
setting is set to on
, it will behave as you expect
I'm going to re-flag this as a potential enhancement, as the behavior is as expected. As noted by @MartinGC94, completion would need to be enabled as a trigger for a space after a parameter, and would need to be done in an efficient detection manner so as not to tie up PSES in the search.
Prerequisites
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
Visual Studio Code Version
Extension Version
Steps to Reproduce
Visuals
No response
Logs
No response