Use this page to activate integration with the TSLint code verifier and configure its behaviour.
|Enable||Select this checkbox to activate TSLint in the current project. After that the other controls in the page are enabled.|
|Node Interpreter|| In this field, specify the Node.js interpreter to use. If you choose the |
In most cases, CLion detects the project default interpreter and fills in the field itself. You can also choose another configured local interpreter or click and configure a new one.
|TSLint Package|| In this field, specify the location of the |
|Configuration File|| In this area, appoint the configuration to use. By default, CLion first looks for a tslint.json, tslint.yaml, or tslint.yml configuration file. CLion starts the search from the folder where the file to be checked is stored, then searches in the parent folder, and so on until reaches the project root. If no tslint.json, tslint.yaml, or tslint.yml configuration file is found, TSLint uses its default embedded configuration file. Accordingly, you have to define the configuration to apply either in a tslint.json, tslint.yaml, or tslint.yml configuration file, or in a custom configuration file, or rely on the default embedded configuration. |
|Additional Rules Directory||In this field, specify the location of the files with additional code verification rules. These rules will be applied after the rules from tslint.json, tslint.yaml, tslint.yml, or from the above specified custom configuration file and accordingly will override them.|