State of Analyzers? StyleCop and/or ...?
I tried to find some information on what's the current most recommended set of analyzers, but ran into lots of different recommendation.
While StyleCop hasn't really been updated in a long time, it still seems quite popular.
What would be considered the "best" set of analyzers?
21 Replies
Unknown User•4w ago
Message Not Public
Sign In & Join Server To View
its still being updated its just stuck on beta all the time
.net 9 updated some things regarding code analysis which lets you actually enforce all of the default ones on build https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/overview?tabs=net-9
Code analysis in .NET
Learn about source code analysis in the .NET SDK.
but rider still doesnt support this newer editor config format
so stylecop is still the most reliable
Unknown User•4w ago
Message Not Public
Sign In & Join Server To View
Oh, didn't get any notifications 😅
Yes
Unknown User•4w ago
Message Not Public
Sign In & Join Server To View
It's so odd/annoying that they aren't release just a new version and everyone just accepts the beta tag.
Not like anyone is going to sue them if it has an issue in "stable" version 🤔
Isn't one of the issues though that it only supports up to C# 8
So it has no idea about newer language features?
Unknown User•4w ago
Message Not Public
Sign In & Join Server To View
Does the beta support the newer language features? Kind of unclear from the repo
Unknown User•4w ago
Message Not Public
Sign In & Join Server To View
So I guess the point is, there isn't something that matches StyleCop in power, that's why people still use/recommend it, despite it not being able to support the latest language version and having a forever beta stage?
Unknown User•4w ago
Message Not Public
Sign In & Join Server To View
I get that honestly
Unknown User•4w ago
Message Not Public
Sign In & Join Server To View
I do my fair share of OSS dev 😄
Unknown User•4w ago
Message Not Public
Sign In & Join Server To View
I just find that the analyzer situation is in a very confusing state and it's hard to understand what one should use
TeBeCo
you also need to ANYWAY create a proper editor config
and add
dotnet format --check-for-no-change-read-the-docsQuoted by
<@689473681302224947> from #State of Analyzers? StyleCop and/or ...? (click here)
React with ❌ to remove this embed.
Unknown User•4w ago
Message Not Public
Sign In & Join Server To View
I guess it would help a lot if the readme clarified the state of things.
Maybe there is already, but some sort of roadmap would be useful to see what is required to get to a next "stable" version and where the beta version is at.
Trying to catch-all before releasing is just a losing battle with how fast .NET/roslyn is moving and having to play catch up in their personal time
Guess, I'll see if I can add some points. First gotta fix that codecov badge 😄
Welp tests are failing, maybe that needs fixing first 🙃