PrimalSense Not AutoCompleting Parameters

[kellydavies]

Product, version and build: PowerShell Studio 2017 (5.4.143) 64-bit
Operating system: Windows 7 Enterprise Edition (64-bit) or Windows 10 Enterprise Edition (64-bit)

The autocomplete feature in the PowerShell Studio script editor does not appear to be working for parameters with ValidateSet validation rules. The issue occurs whether for custom functions that use the ValidateSet rule or for built-in PowerShell cmdlets.

For example, the -Expand parameter in Format-Table has only three enumerated options: Both, CoreOnly, EnumOnly. When adding the command to a script in PowerShell Studio, the tab autocomplete feature will add the -Expand parameter to the code line but will not display the set of available options. On the other hand, when editing the script in PowerShell ISE, using the -Expand parameter with Format-Table will cause the list of available options to appear.

The other PrimalSense features such as colour coding of commands and parameter names, the TAB to add all available parameters, etc. all seem to work.

[davidc]

I'm able to get PrimalSense for the Validation set when it comes to custom function declared in the script. As for core cmdlets, the cached information doesn't include that validation set information, but this is something we hope to address in the future.

[kellydavies]

Ok, I dug a little further regarding the custom functions.

You are correct that it works with custom functions in a .PS1 file, but as soon as the .PS1 file is converted to a module, PowerShell Studio will no longer complete the parameter values while the PowerShell ISE will continue to successfully autocomplete.

[davidc]

Yes, this is because modules are cache by the application and that information is not retained.

[kellydavies]

Ah, makes sense. Disappointing, but makes sense.

Thanks.