It’s another busy week in our Community, and we want to say thanks to everyone who prompted interesting discussions and gave us feedback on Sonar products that will help us continuously improve.
Java Rule Feedback:
@reitzmichnicht suggested a rule that using
assertshould not be possible in public code. While there’s a case to be made for using
assertin private methods, this discussion prompted us to extend
java:S4272to apply to protected and package-protected methods. SONARJAVA-4565
C/C++ Rule Feedback:
Last week @l0cky3r gave some feedback on a rule that helped us create some tickets for our Java analyzer, and this week he helped us realize that it applied to our C/C++ analyzer as well: which helped us create CPP-4234. 2-for-1 special!
Thanks to @Theramar who reported a false-positive on
cpp:S905that is the result of a parsing error on the
std::to_arrayidentifier, which needs to be fixed as a part of our support for C++20. CPP-4608
Swift Rule Feedback:
Over time, a couple users (@ladislas, @Darotudeen_Durosomo, @cbh2000, @Daniel_Sanchez_Cisne) have reported issues with
swift:S3087on SwiftUI code. Now there’s a ticket to address this: SONARSWIFT-541
Another good catch on the Swift programming language: this time regarding
swift:S1144and reported by @frugoman. SONARSWIFT-542
TypeScript Rule Feedback:
- Detecting unused imports (
typescript:S1128) is surprisingly tricky, and another corner case was shared by @zhijie.hao which helped us create SonarSource/SonarJS #4047
Have you heard about SonarLint? While SonarQube and SonarCloud help catch issues in your CI/CD, SonarLint helps you find and fix issues while you code right in your IDE of choice. It’s an invaluable addition if you’re already using the Sonar solution.
This week we got a lot of helpful feedback from our Community.
@Rebse tops the Leaderboard this week. That’s not actually an unusual situation. Gilbert is well known for the time he takes to help other users, and this week was no exception. We all deeply appreciate your contributions, Gilbert.
Deprecation of Java 11 runtime
This week we announced that running analysis with Java 11 is now considered deprecated. A few things… have to happen first, and maybe not everything happened in the right order. Piece by piece, we’re getting our ducks in a row, but thanks to a few folks:
There seem to be some users experiencing an issue with the newest version of the Scanner, particularly when the scanner tries to execute other programs. Thanks @Gilthoniel, @ZoranIlievski, @xavi, @jrouwe and @Jonathan_Schweikhart for the reports. There’s even a community pull request that has been prepared (with a workaround in the comments) – hopefully we can sort this out soon
Once more, we extend our thanks to everyone mentioned here - and those we may have missed - for their efforts in strengthening this community and enhancing our Sonar products. Two special thanks this week:
Please leave your own recognitions below – whether for another community member or a SonarSourcer who assisted you this week. If there’s someone you think should be acknowledged in next week’s roundup, don’t hesitate to let us know.