Release notes
This version switches to SonarQube™ 5.1 API. This version no longer supports any earlier versions than version 5.1 of SonarQube™.
Improvements:
- Support for SonarLint - setup instructions
- Now supports SonarQube™ API 5.1
- Switched to Java 1.7
- The Salesforce API version in package.xml is now honoured
- Asynchronous and ‘History Only’ options for running unit tests
- A new pseudo-rule called ‘An Exception has Occurred’ which shows CodeScan parsing errors. Parsing errors can occur if CodeScan can’t parse the file correctly (due to a syntax error or an un-implemented language parsing feature). Please contact support@code-scan.com so that we can fix the parsing of this file - please include a small snippet of the surrounding code so we can diagnose the problem.
- Aura & Lightning Support (3.5-f)
Parsing fixes:
-
Supports exact equality expression correctly
boolean c = a === b;
-
Supports non top-level explicit constructos
class foo{ public foo(){ if ( true ) super(123); } }
-
Handle SOQL comments and escaping correctly. For example:
object y = [ SELECT id FROM Account WHERE //comments also work Name LIKE ‘\%%’ OR Name LIKE ‘\_%’ ];
-
Handle Keywords in label names (fixed in 3.5b)
andSystem.label.void;
Component.Apex.OutputLabel lbl = …; System.debug(lbl.void);
-
Handle Keywords in label names (fixed in 3.5f)
andSystem.label.void;
Component.Apex.OutputLabel lbl = …; System.debug(lbl.void);
-
Fix SOQL statements in outer statements (fixed in 3.5f)
if( !([select Fooc from Somethingc where id=:someId()].Foo__c) )…
Bug Fixes
- Fixed a bug introduced in 3.5-RC3 which causes unit testing to fail
- Fixed a bug with licensing when machine has no loopback address
- Fixed a versioning issue in force-versions download (3.5-e)
- Fixed several async/history unit tests bugs (3.5-k)
- Fixed a bug in the symbol table resolution
- Fixed some bugs in force-versions API for downloading and commits to git (3.5-k)
- Fixed a bug in history building when the related class for a result is deleted (3.5.15)