category-roslynator.severity not working #875
Replies: 6 comments 4 replies
-
Hi, I've published new version that fixes this bug. Please install latest version. Thanks for understanding. |
Beta Was this translation helpful? Give feedback.
-
Hi, I should probably release nugets as 4.0.1, it would be more clear. But because previous version was 4.0.0-rc I did not want to skip 4.0.0. Regardless of this confusion, the nuget 4.0.0 are newest nugets and they contain the fix. |
Beta Was this translation helpful? Give feedback.
-
When I run Versions
I specifically set some RCS severity to Is there any other configuration that is needed for .net6.0? Note: The RCSxxxx errors along with CAxxxx are being reported both by cli and viscose plugin when using .net5 |
Beta Was this translation helpful? Give feedback.
-
Can you please run |
Beta Was this translation helpful? Give feedback.
-
That's unfortunate. But I have suspicion that this is not Roslynator error but MSBuild locator error which is a Microsoft library Roslynator relies upon. You can see it in a call stack as I would suggest to check their repo and file an issue there. |
Beta Was this translation helpful? Give feedback.
-
Hi @chanakya-svt, It's good that you raised the issue in the Locator repo. I think we should wait for them to answer before making any further assumptions. |
Beta Was this translation helpful? Give feedback.
-
I set the following setting in
.editorconfig
file. None of the RCS#### errors are being picked up in VSCode or via CLIv0.3.1
VSCode version: 1.63.2
Dotnet: v5
Roslynator.Analyzers: v4.0.0-rc
Roslynator.CodeAnalysis.Analyzers: v4.0.0-rc
Roslynator.Formatting.Analyzers: v4.0.0-rc
roslynator.dotnet.cli(globally installed): v0.3.1
I used the configuration from here
Is there anything else I need to setup for this to work or I need to set individual severity for each ANALYZER_ID?
Beta Was this translation helpful? Give feedback.
All reactions