Hello Sonar Community!
It has been a slower week in our Community. Many SonarSourcers are on vacation, as no doubt are many of our dear community members. Leith is on vacation right now. My vacation is at the end of the month (Toulouse / Carcassonne / Paris!), and Ann will take off the week after that. With a new LTA coming up at the end of this year, we know it won’t stay quiet forever…
We’re grateful every time you give us feedback, so like every week we want to spend some time acknowledging everyone who prompted interesting discussions and gave us feedback to help us continuously improve.
SonarQube:
- Thanks @CrushaKRool, for suggesting that we add more specific guidance about what parameters to feed
stylelint
to get a report compatible with SonarQube’s external issues feature. We’ll update the docs tout suite!
SonarCloud:
- Thanks @sodul for reporting that the documentation link in the footer of SonarCloud is pointing not to the docs but…. to SonarCloud. Whoops. We will fix that.
SonarLint:
-
SonarLint for IntelliJ is currently unable to find opened files when in a WSL or dev container. Thanks for the report @andz! SLI-1538
-
In SonarLint for Visual Studio, @Brun0oO found a bug (a
NullReferenceException
on startup) that has already been fixed in v8.2.1! Thanks! SLVS-1336 -
Findings from multiple config scopes should not get reported for a specific config scope – I’m not sure what that means, but it was causing trouble for @Nadine_Seibel and is being fixed by SLCORE-917! Thanks!
Rule & Language Improvements:
java:S3457
is raising false-postives on LaTeX code and other formats that have\\n
as part of keywords in their syntax. Thanks @ivan-igorevich! SONARJAVA-5098
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