Hello Sonar Community!
Like every week we want to spend some time saying thanks to everyone who prompted interesting discussions and gave us feedback on Sonar products that will help us continuously improve.
SonarQube:
-
SonarQube v10.4 introduces v2 of SonarQube’s Web API, and early adopter @Mikaciu tried using it but came up short when specifying the
Content-Type. We figured it out and sent it over to the right team to make sure this is documented. Thanks! -
@Uladzislau_Yarmolin noted that analysis with SonarScanner for Gradle fails when the configuration cache is enabled. We really appreciate the work he did to whittle the problem down from the complex environment where he encountered the problem to the compact reproducer he provided, and the time he took in discussion to help us understand the problem! We’ve created SONARGRADL-137 to address it.
SonarCloud:
- We’ve worked quite a bit on accessibility over the last few years, but we still have our blind spots* (
), and @bmct pointed one out when he noted that he was having trouble with our colored coverage markers in the code viewer. Thanks! We’ll get it fixed.
*Ann wrote this, do not send me letters.
SonarLint:
-
Thanks @AbitFishy for pointing out that the quick fix for
cpp:S5955is removing variables unrelated to the issue raised. We’ll fix that with CPP-5057! -
Another quick-fix gone amiss was reported by @daveh, this time concerning
csharp:S2178. Thanks for the heads-up. SonarSource/sonar-dotnet #8834
Language & Rule Improvements:
-
Shoutout to @yago for adding another case to an existing false-positive report SonarSource/SonarJS #2410!
-
Thanks to @Jos_Abrahams for letting us know about a false-positive concerning
cobol:S1570! SONARCOBOL-1697. -
Beauty may be in the eye of the beholder, but proper indentation is quantitative. At least, we thought so, but @stl543 uses tabs instead of spaces, and that caused problems with
java:S120, which we’ll fix with SONARJAVA-4894. -
@bers provided a tidy little reproducer for the false-positive they found in
python:S5644. That let us diagnose the problem quickly and create SONARPY-1676 for the fix. -
Heuristics are, by nature, imperfect. @Richardissimo ran up against that with
csharp:S125, and a line in a natural-language comment that happened to end with a semicolon. We’ll address it with sonar-dotnet#8819. -
@klavtone had the sense that something was going sideways with
python:S5727. His elegant little reproducer helped us create SONARPY-1675 to address it.
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.
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.
Colin, @ganncamp, and @leith.darawsheh