Consider adding `RS0030` to the current CsWin32 suppressions list
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.5k
- Forks
- 124
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 9
Description
Is your feature request related to a problem? Please describe.
In my own code, I make use of Microsoft.CodeAnalysis.BannedApiAnalyzers ensure development is steered in a way which I'd like for my project. I recently banned a symbol that's used extensively within CsWin32, and that's fine that it's used there, but I'd prefer to not use it in my own code, however that's very cumbersome to achieve via the .editorconfig file, etc.
Describe the solution you'd like
CsWin32 already suppresses a large amount of analyser warnings, so I don't see why RS0030 couldn't be added to the list also.
Describe alternatives you've considered
Not ban the symbol in general, or do twists and contortions with my .editorconfig file to try and sliver my requirements through.
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 does not name a file or test. Locate CsWin32's current analyzer-suppression list, review how existing suppressions are declared, and check how RS0030 is handled in a generated project. Done means the requested suppression is included without requiring users to alter their own .editorconfig settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100