fix: resolve CC012 None by symbol identity#31
Merged
Conversation
A custom CancellationToken-valued property named None can carry meaningful cancellation state. Requiring the framework property symbol prevents the analyzer and fixer from replacing that behavior.
This was referenced Jul 21, 2026
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.
Summary
.Noneto resolve to the actual staticSystem.Threading.CancellationToken.Nonepropertydefaultanddefault(CancellationToken)behavior unchangedNoneWhy
CC012 previously matched member syntax by its final identifier only. A custom property named
Nonecould carry a canceled or otherwise meaningful token, yet the analyzer and fixer would suggest replacing it with an unrelated in-scope parameter.Validation
Known repository baseline
The repo-wide style verifier continues to report the existing IDE0011 brace backlog. No new whitespace issue exists in the touched C# files.