Sonar Community Roundup, July 13 - July 19

Hello Sonar Community!

Coming to you live from the WeAreDevelopers World Congress in Berlin! As always, it’s amazing to come to these conferences where everyone comes up to our booth to tell us how much they love Sonar! And of course, like you all, they give us plenty of feedback. :laughing:


With our brilliant Events manager, Emma!

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:

SonarLint:

SonarCloud:

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

1 Like

Hey Colin, I made this point in the thread but nobody there seems to have picked up on it. Issue SONARPHP-1503 is NOT specific to PHPstan, it affects Psalm reports as well, and seems to affect ALL reports, not just “certain” phpstan reports. As far as I can tell this blocks ANY sort of PHP linting.

I want to make that clear because it doesn’t appear that anyone has looked at it yet and I’d expect the priority to be a bit higher considering the fact that it seems to be totally broken. If it is NOT totally broken and is in fact working for some people, I’d really appreciate if someone can let myself and the original reporter know an effective workaround.

Thanks,
Ian