GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add missing Severity entry for `Invoke-ScriptAnalyzer` docs by liamjpeters · Pull Request #2193 · PowerShell/PSScriptAnalyzer

Conversation

@liamjpeters

@liamjpeters Liam Peters (liamjpeters) commented Jul 20, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

PR Summary

The -Severity parameter of the Invoke-ScriptAnalyzer command has 4 allowed values.

PSScriptAnalyzer/Engine/Commands/InvokeScriptAnalyzerCommand.cs

Lines 148 to 159 in 4b0117c

/// <summary>
/// IncludeRule: Array of the severity types to be enabled.
/// </summary>
[ValidateSet("Warning", "Error", "Information", "ParseError", IgnoreCase = true)]
[Parameter(Mandatory = false)]
[SuppressMessage("Microsoft.Performance", "CA1819:PropertiesShouldNotReturnArrays")]
public string[] Severity
{
get { return severity; }
set { severity = value; }
}
private string[] severity;

The docs are missing ParseError as an allowed value.

Fixes #2192

Does not conflict with #2190

PR Checklist

  • PR has a meaningful title
    • Use the present tense and imperative mood when describing your changes
  • Summarized changes
  • Change is not breaking
  • Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
  • Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
  • This PR is ready to merge and is not Work in Progress.
    • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@liamjpeters
Add missing Severity entry
317240d
Copilot AI review requested due to automatic review settings July 20, 2026 10:28
@liamjpeters
Liam Peters (liamjpeters) requested review from a team, Mikey Lombardi (He/Him) (michaeltlombardi) and Sean Wheeler (sdwheeler) as code owners July 20, 2026 10:28
Copilot started reviewing on behalf of Liam Peters (liamjpeters) July 20, 2026 10:29
View session
Copilot AI reviewed Jul 20, 2026
View reviewed changes

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Invoke-ScriptAnalyzer cmdlet documentation to match the actual allowed -Severity values implemented in InvokeScriptAnalyzerCommand (including ParseError).

Changes:

  • Add ParseError to the documented valid values for -Severity.
  • Normalize the valid-values list formatting (remove trailing punctuation from Information).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
Comment thread docs/Cmdlets/Invoke-ScriptAnalyzer.md Resolved

Uh oh!

There was an error while loading. Please reload this page.
@liamjpeters
Fix typo "Ore" instead of "Or"
9fb8c92 
Co-authored-by: Copilot Autofix powered by AI <[email protected]>
sdwheeler
Sean Wheeler (sdwheeler) approved these changes Jul 23, 2026
View reviewed changes

@sdwheeler Sean Wheeler (sdwheeler) left a comment

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
liamjpeters reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
@liamjpeters

Liam Peters (liamjpeters) commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

Test failures are unrelated to this. They're the Windows test picking up Pester v6. Addressed that in #2194
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@sdwheeler Sean Wheeler (sdwheeler) mentioned this pull request Jul 23, 2026
Sync docs changes from docs repo #2196
Merged
bergmeister
Christoph Bergmeister (bergmeister) approved these changes Sep 14, 2026
View reviewed changes

@bergmeister Christoph Bergmeister (bergmeister) left a comment

Copy link
Copy Markdown
Collaborator

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@bergmeister
Merge branch 'main' into CmdletDocsUpdate
0c1e743
@bergmeister
Christoph Bergmeister (bergmeister) requested a review from Andy Jordan (andyleejordan) September 14, 2026 20:17
@bergmeister
Christoph Bergmeister (bergmeister) merged commit 57431f8 into PowerShell:main Sep 14, 2026
4 checks passed

Uh oh!

There was an error while loading. Please reload this page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot
Copilot review effort
Applies to this pull request for everyone.Learn more about Copilot code review.
Copilot left review comments
@bergmeister Christoph Bergmeister (bergmeister) bergmeister approved these changes
@michaeltlombardi Mikey Lombardi (He/Him) (michaeltlombardi) Awaiting requested review from michaeltlombardi michaeltlombardi is a code owner
@andyleejordan Andy Jordan (andyleejordan) Awaiting requested review from andyleejordan
+1 more reviewer
@sdwheeler Sean Wheeler (sdwheeler) sdwheeler approved these changes
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

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

Uh oh!

There was an error while loading. Please reload this page.

4 participants

@liamjpeters @bergmeister @sdwheeler
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.