TSLint was introduced in version CI 9 of Webclipse.
TSLint is an extensible linter for TypeScript. While our existing TypeScript validator will already find syntax errors in your code, TSLint checks your code for readability, maintainability, and functionality errors – allowing you to fix them before running into them in production, at runtime.
So, how does our integration work? For Angular projects, a tslint.json is created in your project’s root folder; we use the settings in this configuration file when linting your project. Issues noticed are marked as warnings in the editors ruler area and in the Problems view. This ensures your Angular project conforms to NG best practices.
A key feature is our quick fix support – you can fix the problem automatically, remove the linting rule if you don’t like it, or simply turn off linting for the entire project. The number of quick fixes available right now are limited, but we’re working on adding more to the tooling soon.
TSLint can catch a number of potential problems – from style issues like whitespace and indentation, to functionality issues like duplicate variables, unused expressions or variables used before they are declared. For a more complete list, please see: https://palantir.github.io/tslint/rules/.
We’re also working on adding better support for the tslint.json file, so it’s easy to get to the linting settings you really want for your team.