Unused analyzers: disable in VS when file has errors#19892
Open
auduchinok wants to merge 5 commits into
Open
Conversation
Contributor
❗ Release notes required
|
github-actions
Bot
added
the
AI-Tooling-Check-Scanned-Clean
auduchinok
added
NO_RELEASE_NOTES
Member
Author
|
@T-Gro This is ready. Feel free to add VS-specific tests to this branch, like the ones in the other PR. |
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
1 participant
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.
An alternative take on #19854.
The FCS APIs work correctly with the check results they are passed in, so the decision on whether to call them should be done on the client side.