FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Invoke-ScriptAnalyzer: Include parse errors in reported error count by MatejKafka · Pull Request #2069 · PowerShell/PSScriptAnalyzer · GitHub

Invoke-ScriptAnalyzer: Include parse errors in reported error count - #2069

Merged
Andy Jordan (andyleejordan) merged 1 commit into
PowerShell:mainfrom
MatejKafka:report-summary-parse-errors
Mar 13, 2025
Merged

Invoke-ScriptAnalyzer: Include parse errors in reported error count#2069
Andy Jordan (andyleejordan) merged 1 commit into
PowerShell:mainfrom
MatejKafka:report-summary-parse-errors

Conversation

Copy link
Copy Markdown
Contributor

PR Summary

Previously, parse error were not reported in the summary. With this PR, the exit code from -EnableExit matches the number of diagnostics reported by -ReportSummary and parse errors are included under errors. Since -ReportSummary output is sent directly to the host, I don't believe this to be a breaking change.

PR Checklist

Previously, parse error were not reported in the summary. With this commit,
the exit code from -EnableExit matches the number of reported issues.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants


Back | FazBrowse Home | New Git URL