SonarSource is pleased to announce the release of SonarLint for IntelliJ version 2.0.
SonarLint for IntelliJ 2.0 provides the new connected mode that meets all those needs. With this version, you can now establish a connection to a SonarQube server (version greater than 5.2) :
Then, you can bind your IntelliJ project with the corresponding one on the SonarQube server:
And that’s all! Once a project is bound to a SonarQube server, SonarLint will automatically use the right set of rules defined in the quality profile configured for this project on SonarQube.
Note that this connected mode currently does not support commercial plugins – but this will come soon.
- Function parameters with default values should be last(bug, es2015)
- Attempts should not be made to update “const” variables (bug, es2015)
- Class names and file names should match (confusing, es2015)
- Default parameters should not cause side effects (es2015, pitfall)
- Generators should “yield” something (es2015, suspicious)
- Shorthand object properties should be grouped at the beginning or end of an object declaration (convention, es2015)
- Unchanged variables should be marked “const” (es2015)
- “enum” fields should not be publicly mutable (bad-practice, security)
- Abstract methods should not be redundant (confusing)
- Child class methods named for parent class methods should be overrides (pitfall)
- Raw byte values should not be used in bitwise operations in combination with shifts (bug)
- String function use should be optimized for single characters (clumsy, performance)
Have fun with SonarLint !