Sonar Community Roundup, June 1 - 7 🏳️‍🌈

Hello Sonar Community!

Summer is almost here, isn’t it time for you all to go on vacation and leave us alone? :pray: :sweat_smile:

Just kidding. But hey, if you’re out there, tell us your summer plans. City break? Beach? Visiting a new country? I’m headed to Paris Pride at the end of the month (happy Pride Month to those who celebrate, and heck, to those who don’t) but I don’t have anything else planned. I’m looking for ideas. :eyes:

Back to business – It’s been a big week here in the Community, with lots of help and guidance from you, our members, to improve our products and your experience with them.

We’re grateful when you take the time to do that, 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.



  • When SonarQube sends information about changed Taint Vulnerabilities to SonarLint for Eclipse, we assume that at least one file with such a Taint Vulnerability is currently opened in the editor. That’s not always a safe assumption and leads to an error. Thanks for the report @gnl42! SLE-877


Rule & Language Improvements:

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


It’s winter in the southern hemisphere.