Invoke-ScriptAnalyzer does not report a parse failure in a param() block caused by a missing parameter separator comma.

[FabrizioMarana]

Steps to reproduce

param (
    [string[]]$aszServers = @()
    [string]$fServerListFile = ""
)

Expected behaviour

Invoke-ScriptAnalyzer should report a parser-related error because the parameter list is malformed (missing comma between parameters).

Actual behaviour

PowerShell detects the syntax error:

> .\Broken.ps1

At line:2 char:29
+     [string[]]$aszServers = @()
+                             ~
Missing ')' in function parameter list.

However:

> Invoke-ScriptAnalyzer .\Broken.ps1 -Severity Error

returns nothing.

Environment data

$PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.26100.8655
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.26100.8655
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PSScriptAnalyzer: 1.25.0

[liamjpeters]

👋 Fabby (@FabrizioMarana),

This is expected. There are actually 4 severities. Information, Warning, Error, ParseError.

Invoke-ScriptAnalyzer .\Broken.ps1 -Severity Error

Your example asks only for the Error severity diagnostics. Either omit it, or ask for the ParseError severity diagnostics.

Invoke-ScriptAnalyzer .\Broken.ps1 -Severity ParseError

RuleName                            Severity     ScriptName Line  Message
--------                            --------     ---------- ----  -------
MissingEndParenthesisInFunctionPara ParseError   Broken.ps1 2     Missing ')' in function parameter list.
meterList
UnexpectedToken                     ParseError   Broken.ps1 4     Unexpected token ')' in expression or statement.

Hope that helps!

[FabrizioMarana]

Huh! I'm an idiot! I never knew! 😁 Thank you very much!!! Please close issue!

P.S. On my version: get-help Invoke-ScriptAnalyzer -parameter Severity gives:

-Severity <String[]>
    After running Script Analyzer with all rules, this parameter selects rule violations with the specified severity.
    Valid values are:
    - Error
    - Warning
    - Information.

    You can specify one ore more severity values.

but ParseError does work!!! 🎉

[liamjpeters]

Thanks for flagging the docs issue 🙂! I've raised a PR to get that fixed.