Repository navigation
Invoke-ScriptAnalyzer does not report a parse failure in a param() block caused by a missing parameter separator comma. #2192
Description
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 Errorreturns 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
Activity
[-]Invoke-ScriptAnalyzer does not report a parse failure for a script containing a malformed param() block caused by a missing parameter separator comma.[/-][+]Invoke-ScriptAnalyzer does not report a parse failure in a param() block caused by a missing parameter separator comma.[/+]liamjpeters commentedon Jul 20, 2026
👋 Fabby (@FabrizioMarana),
This is expected. There are actually 4 severities.
Information,Warning,Error,ParseError.Your example asks only for the
Errorseverity diagnostics. Either omit it, or ask for theParseErrorseverity diagnostics.Hope that helps!
FabrizioMarana commentedon Jul 20, 2026
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 Severitygives:but ParseError does work!!! 🎉
liamjpeters commentedon Jul 20, 2026
Thanks for flagging the docs issue 🙂! I've raised a PR to get that fixed.