RCS1016 .editorconfig
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 294
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 4
Description
**Product and Version Used**:
VS2019 (16.6.1)
I have found a strange behavior.
If i configure the analyzers in a ruleset file and set RCS1016 to "warning", VS2019 (16.6.1) shows this correcty as a warning for a simple one line method and provides the right fix.
If i configure the analyzers in .editorconfig and set RCS1016 to "warning", nothing happens.
Other analyzers are enabled in the right way, and also the severity seems to be right.
Except for RCS1016.
Contributor guide
Research direction
Reproduce the issue in VS2019 16.6.1 using Roslynator.Analyzers 2.3.0 and a simple one-line method. Compare RCS1016 configured as a warning in a ruleset file with the same setting in .editorconfig, including whether the diagnostic and code fix appear. Done means the .editorconfig configuration produces the expected warning and fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100