This repository has been archived by the owner on Jul 12, 2022. It is now read-only.
Diagnostic logging fixes #238
Open
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
SARIF logs were being incorrectly generated since each error class (syntactic/semantic/etc) was calling LogDiagnostics upon completion. Now all Diagnostics are aggregated together at the end of analysis and then logged, producing a proper JSON output.
I'd merged the 1.3 Roslyn upgrade branch (PR here #237) from my machine in here to make sure these changes still worked with the new SARIF format. I recommend just browsing the .cs changes or going commit by commit and just looking at the first 2 commits.