Vscode-powershell: Wildcard commands aren't auto-completing

Created on 21 Apr 2016  路  10Comments  路  Source: PowerShell/vscode-powershell

In the PowerShell ISE, I frequently type partial command names, containing wildcards. For example, to find the command New-AzureRmVirtualNetworkSubnetConfig, I might type *subnet* and hit CTRL + SPACE to invoke Intellisense.

Unfortunately, this isn't currently working in the Visual Studio Code PowerShell Extension.

image

image

image

image

Here's a screenshot showing it working in PowerShell ISE. Forgive the fading-out Intellisense, due to some issue with screen capture in SnagIt.

image

Cheers,
Trevor Sullivan
https://trevorsullivan.net
https://twitter.com/pcgeek86

Area-IntelliSense Issue-Bug

Most helpful comment

All 10 comments

I'll bet that this is an issue on VS Code's side. They add some extra "intelligence" when it comes to gathering completions at the cursor location so they might be throwing out the results that come back from the language server in this case. I'll look into it!

Moving to 0.7.0, definitely looks like an issue on VS Code's side. I see that IntelliSense results are coming back for wildcard completions but they aren't being displayed. Will file a bug at their repo to track this.

@daviwil Thanks for discovering the root cause! Hoping they can fix this soon.

@daviwil Any update on this? I'm still encountering this bug. Thanks!

Nah, too many other high priority issues recently. I'll assign it to the next feature update in case we get a chance to look into it.

@tylerl0706 If we could figure out what's going on here, this would help bring the VSCode development experience in line with the console experience. Let me know if I can help clarify the issue at all.

@daviwil did you ever get the chance to open that issue on VSCode?

@TylerLeonhardt your dependent issue was closed, asking you to ask over at the extensions slack for help on it (strangely)

Yep, we need to implement this but unfortunately the platform doesnt give us a good mechanism yet.

Was this page helpful?
0 / 5 - 0 ratings