Add analyzer to identify anti-patterns in usage
Open
Nobody has claimed this yet.
analyzers
enhancement
- Dominant language
- C#
- Stars
- 2.5k
- Forks
- 124
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 9
Description
Consider analyzers to train users to avoid such syntax as:
== true or == new BOOL(true) to test a BOOL type.
Originally posted by @AArnott in https://github.com/microsoft/CsWin32/discussions/584#discussioncomment-3180324
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or analyzer entry points. Start by locating the repository's analyzer or source-generator integration and define the supported BOOL anti-pattern cases; done should mean those examples produce useful diagnostics with coverage for the reported syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100