We are upgrading profiles for one of our customers and I noticed that in this update, some very thoughtful rules are now deactivated by default in Sonar Way.
In my opinion, these rules are valid and meaningful, and they make sense to be included. For example:
For instance, “Methods should not be too complex”, java:S1541 was removed from Sonar way quite a few years ago in favor of java:S3776, “Cognitive Complexity of methods should not be too high”. How far back are you looking in your change log?
You’re right — maybe the screenshot or the rule I picked wasn’t the best example of what I wanted to point out. This is an old instance we still maintain for one of our customers. It’s possible that the “Methods should not be too complex” rule was something we disabled ourselves — I just happened to capture that one.
I really appreciate the info you shared; it’s definitely helpful to keep in mind.
That said, I’m wondering: why aren’t these rule changes reflected in the changelog?
Is there anything we could do to improve how rule changes are communicated? Maybe a shared space to document them? Or even a note on deprecated rules, something like “This rule has been replaced by rule X”, to help track the evolution?
How old? We did work… last year? The year before? To be more transparent about the impact of rule updates. There are also updates here in the Community when new rules are released on SonarQube Cloud (with the note that they’ll appear in the next on-prem versions).
