SonarLint for IntelliJ 8.2 - Analysis of Infrastructure as Code files, better code examples display

Hello SonarLint for IntelliJ users,

a new version of SonarLint has been released that will help you write cleaner and more secure code for different Infrastructure as Code domains. In fact SonarLint can now analyze the following files (you can follow the links to see which detections are available):

Please note that as of today, the majority of available rules for those domains are Security Hotspots, which are only available in SonarLint for IntelliJ if you use connected mode with SonarQube 9.7+.

We’ve also made further improvements to our rule descriptions; in fact, we started this journey a few months ago by introducing a new format for rule descriptions, then we introduced Clean Code principles and automatic patch selection, and in this month’s release we’ve been working to help you easily understand and act on the noncompliant/compliant code examples: we’ve added syntax highlighting and code diff highlighting between non-compliant and compliant code examples in our rule descriptions:

The code diff highlighting is only available for rules descriptions migrated to the new format, and we’re progressively migrating all existing rules to the new format.

This release adds several new detections, here is a selection:

  • 3 Java rules that cover design and architecture good practices for Monster Class, Brain Method and Singleton.
  • 9 new rules to help Java developers writing Kotlin idiomatic code.
  • 8 new JavaScript code quality rule.
  • new Python rules and quick fixes related to type hints and regular expressions.

The full release notes are here.