Question

Do you use .editorconfig rules as informational warnings or linting rules? In a diverse team with developers of different levels of experience, we found undesirable results with both options.

Background

After adding .editorconfig from https://github.com/dotnet/roslyn/blob/main/.editorconfig and committing it to git, we found hundreds of violations in our solution. In Visual Studio 2022, this creates lots of noise in the Errors List, especially IDE0055 on line 42.

Information Warnings

Because of all that noise, many developers completely ignore the warnings tab. This was not what I intended by adding .editorconfig to the solution.

Linting Rules

Some developers have auto-format on save turned on, so saving creates many unintentional changes to any source file and makes code review difficult because the number of formatting changes makes it difficult to see what the author actually changed. This also is not what I intended. From my perspective, this is the least desirable option because it creates so much change in the source code.

More developers, more IDEs, more problems

Most developers use Visual Studio 2022. Two developers, myself included, use JetBrains Rider because it is so much more efficient, but it doesn't even show IDE0055 warnings. I'm starting to suspect IDE0055 is more finicky and more trouble than it is worth, but disabling code analysis is definitely not what I was after by adding it to the project.