Wildcard commands aren't auto-completing

[pcgeek86]

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.

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

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

[daviwil]

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!

[daviwil]

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.

[pcgeek86]

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

[pcgeek86]

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

[daviwil]

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.