Repository navigation
Suppress incorrect CA2257 warnings - #1509
Merged
Sergio Pedri (Sergio0694) merged 1 commit intoFeb 21, 2024
Merged
Sergio Pedri (Sergio0694) merged 1 commit into
Sergio Pedri (Sergio0694) merged 1 commit into
Conversation
Sergio Pedri (Sergio0694)
requested a review
from Manodasan Wignarajah (manodasanW)
February 21, 2024 01:12
Manodasan Wignarajah (manodasanW)
requested a review
from Jeremy Koritzinsky (jkoritzinsky)
February 21, 2024 01:17
Member
|
Related to dotnet/roslyn-analyzers#7106 |
Manodasan Wignarajah (manodasanW)
approved these changes
Feb 21, 2024
Jeremy Koritzinsky (jkoritzinsky)
approved these changes
Feb 21, 2024
Sergio Pedri (Sergio0694)
deleted the
user/sergiopedri/suppress-wrong-ca2257
branch
February 21, 2024 19:57
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
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.
This PR suppresses some incorrect CS2257 warnings that were polluting our build output. As per the docs:
This clearly doesn't apply to these cases, since these members were just nested types, and not something you can invoke.