Skip to content

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

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged

Conversation

MatejKafka
Copy link
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

@andyleejordan andyleejordan enabled auto-merge (squash) March 13, 2025 16:28
@andyleejordan andyleejordan force-pushed the report-summary-parse-errors branch from d6d1f36 to 3390d78 Compare March 13, 2025 16:54
Previously, parse error were not reported in the summary. With this commit,
the exit code from -EnableExit matches the number of reported issues.
@andyleejordan andyleejordan force-pushed the report-summary-parse-errors branch from 3390d78 to 38f2c98 Compare March 13, 2025 17:58
@andyleejordan andyleejordan merged commit 8862e51 into PowerShell:main Mar 13, 2025
4 checks passed
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants