Invoke-ScriptAnalyzer: Include parse errors in reported error count #2069
Conversation
This file contains 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
andyleejordan
approved these changes
Mar 13, 2025
andyleejordan
force-pushed
the
report-summary-parse-errors
branch
from
d6d1f36 to
3390d78
Compare
Previously, parse error were not reported in the summary. With this commit, the exit code from -EnableExit matches the number of reported issues.
andyleejordan
force-pushed
the
report-summary-parse-errors
branch
from
3390d78 to
38f2c98
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Summary
Previously, parse error were not reported in the summary. With this PR, the exit code from
-EnableExitmatches the number of diagnostics reported by-ReportSummaryand parse errors are included under errors. Since-ReportSummaryoutput is sent directly to the host, I don't believe this to be a breaking change.PR Checklist
.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.