You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 29, 2022. It is now read-only.
However, currently there are some horrible inconsistencies, bad practices and other (style-)issues which won't be fixed until we rework those charts. This means that these analyzers are going to complain all the time and the project will be flooded with (even more) warnings.
Do we want that?
In other words, when do we want to add those analyzers?
I think, in general, it would be a great idea to add Microsoft.CodeAnalysis.Analyzers and Microsoft.CodeAnalysis.FxCopAnalyzers to get some support for best practices etc.
However, currently there are some horrible inconsistencies, bad practices and other (style-)issues which won't be fixed until we rework those charts. This means that these analyzers are going to complain all the time and the project will be flooded with (even more) warnings.
Do we want that?
In other words, when do we want to add those analyzers?
Discussions are welcome below.
CC @SeppPenner
The text was updated successfully, but these errors were encountered: