SonarTS Versions Save

See details of release in this RC

We are starting the feedback period for SonarTS 1.2.0.

In this version we added a rule based on :collision:symbolic execution:collision: : Conditions should not always evaluate to "true" or to "false"

On top of that, as usual there are new everyone-must-enable rules: (see some examples at the bottom)

• Type aliases should be used
• Redundant pairs of parentheses should be removed
• Redundant casts and not-null assertions should be avoided
• Map values should not be replaced unconditionally
• Method parameters, caught exceptions and foreach variables' initial values should not be ignored

Finally, this version improves the configuration options available for SonarQube projects:

• global TypeScript can be used now (#258)
• you can configure the path to the nodejs executable (#202)

If you want to try this release candidate with TSLint:

npm install --dev [email protected]

If you want to try it with SonarQube install the attached jar.

Feedback period is open until Thursday, Nov 23.

Feel free to provide any kind of feedback :raising_hand:, as usual just create a github issue.

---

---

---

See 1.1.0-RC1 for details

We are starting the RFF period for SonarTS 1.1.0.

This version introduces support for multi-language and multi-module projects for SonarQube (#195). Now the plugin explicitly looks for the TypeScript compiler inside of your project and then uses it for analysis.

Of course, there are new rules, and most are bug-detection ones:

• Conditionals should start on new lines
• Collection and array contents should be used
• Getters and setters should access the expected fields
• Multiline blocks should be enclosed in curly braces
• Exception should not be created without being thrown
• Methods should not have identical implementations

All of them are activated in Sonar Way Recommended profile (and in default profile for the TSLint extension).

We also fixed two bugs (#193 and #200) that appeared mostly on Windows, and generally the SonarQube plugin should not suffer anymore when analyzing very large projects. Any beta-testing on large code-bases is especially welcome.

If you want to try the RC with TSLint:

npm install --dev [email protected]

Feedback period is open until Thursday, Oct 26.

Feel free to provide any kind of feedback, as usual just create a github issue.

See 1.0.0-RC1 for details

We are happy to announce the feedback period for SonarTS 1.0.0 :tada: , a static code analyzer for TypeScript.

Main features:

• 20 bug-detection and code-smell-detection rules (based on code-modeling engines : Control Flow, Symbol Table and Live Variable Analysis)
• SonarQube-specific :
  • 2 Standard profiles : SonarWay and SonarWay Recommended (with 60 rules)
  • Optional style and coding-convention rules
  • Code coverage import (sonar.typescript.lcov.reportPaths property)
  • Basic Metrics
  • Duplication detection
• 1 non-opinionated bug-detection ruleset configuration for TSLint

Do not forget:

• download dependencies of the project before doing analysis (e.g. run npm install)
• versions being supported (these or newer): Node.js v6 LTS, TypeScript 2.2

For TSLint users : npm install [email protected] For SonarQube users : Please find jar attached to this pre-release