Sonar Community Roundup, Jan 31 - Feb 6

Hi all,

It looks like most people spent their week celebrating Groundhog Day, because it was pretty quiet here in the Community. Meanwhile, I saw statistics this week that said Punxsutawney Phil’s accuracy is worse than 50%. So his call of 6 more weeks of winter almost certainly means we’re in for an early spring. :tulip::tulip::tulip::grinning_face_with_smiling_eyes:

And now, like every week, we’d like to take a moment to recognize you, the users, who help improve the ecosystem for everyone by sparking valuable discussions and providing feedback to drive continuous improvement in our products.

SonarQube Cloud:

SonarQube Server / SonarQube Community Build:

Rules & Languages Improvements:

  • @Jmanom reported that java:S1166 conflicts with Java’s unnamed exception variables and with java:S7467. We’ve updated java:S1166 so it no longer raises an issue when the catch parameter uses the _ pattern and so that it references java:S7467.

  • @TB-StarcMed showed that the quick-fix for cpp:S1659 rewrites an if with multiple variable declarations into invalid C++ code. We’ve already got a ticket in the backlog for this known issue, but take this report as another vote to get it fixed quickly.

  • @Corniel pointed out that csharpsquid:S1210’s requirement to implement comparison operators for every IComparable type creates noisy issues for private nested types. We’ve created a ticket to relax the rule for such tightly scoped private types so it no longer forces unnecessary boilerplate.

  • @1337_Nerd showed that the implicit RPG *INZSR subroutine is incorrectly flagged as unused by rpg:S1601 even though it runs at program initialization. We’ve already implemented a fix that will be available in the next SonarQube Server release.

  • @Jean_Helou provided a beautifully clear reproducer to show that kotlin:S6518 wrongly flags a call to a Java get() method that isn’t a property accessor. We’re working on a fix that will be released soon.

Thanks again to everyone mentioned here - and to anyone we may have missed - for your ongoing contributions in making this community stronger and helping us improve Sonar products.

If you’d like to give a shout-out to someone, whether a community member or a SonarSourcer who helped you, please do so below. And if there’s someone you think we should acknowledge next week, let us know!

 
Ann

2 Likes