VS2022 - configure severity doesnt work, broken, doesnt do anything..???
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 20.7k
- Forks
- 4.3k
- PR merge metrics
- PR metrics pending
Description
Since whenever I want to make a screenshot, the context menu disappears, you will have to be satisfied with a different image of someone else. If you want better feedback, make better software.
The menu below is about supressing warnings, but when I choose "Supress or configure > Configure severity for all ... > None (or ANY OTHER CHOICE)" - absolutly NOTHING happens. Is this supposed to do nothing? Just show us that vs can give warnings?
The context menu doesnt do anything. So what use is there to show us all this shit? I know what platform Im developing for, I dont need some stupid warning, AND I CANT SUPRESS IT?
I already marked the offending method with [SupportedOSPlatform("windows")], what more do you need??????? Is it not understood what that attribute declares? And yet I get more stupid warnings where I use the method, are you fkn kidding?
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
Start by reproducing the issue in Visual Studio 2022 using the reported warning and the “Suppress or configure > Configure severity” context menu. Check whether selecting any severity changes the warning and whether SupportedOSPlatform("windows") is respected at the reported call sites; done means the configured severity takes effect and the expected platform warnings are handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100