I use a .editorconfig loosely based on the .NET Runtime .editorconfig, and I try to fix all info+ issues by running dotnet format --verify-no-changes --severity info during CI.
The reported issues are not shown in the "problems" tab, but when I hover over the code the linter does show the issue.
The problems tab filter already includes "show infos", but the linter info is not shown.
How do I get the C# devkit .editorconfig linter info level results to show up in the "problems" tab?
E.g.
> dotnet format --verify-no-changes --severity info
.\foo.cs(209,25): info IDE0044: Make field readonly [foo.csproj]`
I use a .editorconfig loosely based on the .NET Runtime .editorconfig, and I try to fix all info+ issues by running dotnet format --verify-no-changes --severity info during CI.
The reported issues are not shown in the "problems" tab, but when I hover over the code the linter does show the issue.
The problems tab filter already includes "show infos", but the linter info is not shown.
How do I get the C# devkit .editorconfig linter info level results to show up in the "problems" tab?
E.g.
> dotnet format --verify-no-changes --severity info
.\foo.cs(209,25): info IDE0044: Make field readonly [foo.csproj]`
1 Answer
Reset to default 0I discovered that if I "quick fix" the issue in VSCode, it offers to change the severity reporting, and I noticed that it modifies the .editorconfig file.
See Code Analysis categories
E.g.:
dotnet_analyzer_diagnostic.severity = warning
# dotnet_analyzer_diagnostic.category-Style.severity = warning
After forcing reporting to be a warning the issues now show up in the "problems" tab.
Still don't know why if problems filter is set to info why info severity is not shown without needing to force a warning?