whitespaceBeforeOpenParen does not add a space between param and paren

[strickdd]

System Details Output

• Operating system name and version
  Windows 10 build 1903

### VSCode extensions:
ms-vscode.powershell@2019.5.0
ms-vscode.vs-keybindings@0.2.0


### PSES version:

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.18362.145
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.145
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

I am experiencing a problem with the "powershell.codeFormatting.whitespaceBeforeOpenParen" setting.

Expected Behaviour

When formatting a PowerShell document, a space should separate the "param" keyboard and the following open paren "(".

Actual Behaviour

When I format a PowerShell document (press Ctrl + K; Ctrl + D), a space is not inserted bewteen the "param" keyboard and the open paren "(".

Attached Logs

Attached logs.zip

Proof of Concept/Example Code

Attached Test-WhitespaceBeforeOpenParen.zip
logs.zip
Test-WhitespaceBeforeOpenParen.zip

[SydneyhSmith]

@strickdd thanks for reporting this, formatting is actually provided by PowerShell Script Analyzer so I am going to move this issue over to that repo.

[msftrncs]

This is going to sound funny, but param isn't a control keyword, and thus why it doesn't fall under this treatment.

The parenthesis of the param keyword is not a conditional expression. Instead, param is kind of treated like a function declaration for formal functions or methods. The examples on MS's PowerShell docs are all this way.

https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_functions_advanced_parameters?view=powershell-6

[strickdd]

@msftrncs thanks for the reply. Is there any way to have this be an option, or is it best to utilize the MS standards and rewrite out coding style guidelines to match?