fixed #13087 - store unmatchedSuppression in AnalyzerInformation
#8173
+302
−65
Conversation
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
Collaborator
Author
|
Requires #8159 to be merged first. |
firewave
force-pushed
the
unmatched-ainfo
branch
from
d54f47c to
514c4e3
Compare
firewave
force-pushed
the
unmatched-ainfo
branch
from
514c4e3 to
f94bc98
Compare
firewave
force-pushed
the
unmatched-ainfo
branch
from
f94bc98 to
30ef794
Compare
|
Collaborator
Author
|
The code is quite horrible and not performant but it will only be executed when you encounter an unmatched suppression which should not be common. This addresses a big chunk of the failures in #7079. After that has been merged and all the remaining suppression issues have been fixed we should be able to clean this up a bit. |
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.
No description provided.