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

Activity

1. Fabby (FabrizioMarana)

   changed the title [-]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.[/+] on Jul 17, 2026
2. liamjpeters commented on Jul 20, 2026

   

   Liam Peters (liamjpeters)

   on Jul 20, 2026

   Contributor

   More actions

   👋 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!

   ❤️React with ❤️1Reacted by Fabby
3. FabrizioMarana commented on Jul 20, 2026

   

   Fabby (FabrizioMarana)

   on Jul 20, 2026

   Last edited by FabrizioMarana

   Author

   More actions

   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!!! 🎉
4. liamjpeters commented on Jul 20, 2026

   

   Liam Peters (liamjpeters)

   on Jul 20, 2026

   Contributor

   More actions

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

   👍React with 👍1Reacted by Fabby
5. Christoph Bergmeister (bergmeister)

   closed this as completedin #2193on Sep 14, 2026