Note: As of April 28th, ESLint is the default linter for TypeScript on Codeac. If you wish to continue using TSLint, it requires configuration via a .codeac.yml file.
To keep TSLint active for your project, you must explicitly enable it in your .codeac.yml file. Additionally, ensure that ESLint is configured to only target your JavaScript files by setting the extensions to .js and .jsx as shown below:
TSLint requires configuration via a tslint.yaml or tslint.json configuration file as detailed in TSLint's documentation.
If you don't specify your custom configuration file we use our default below. We suggest to add your own configuration file into your repository root directory to be able to specify your coding and quality standards.
If you want to move forward to the new ESLint plugin way we have a few suggestions for you:
According to Palantir's blog TSLint has been deprecated in favor of ESLint to join the forces and provide better linting experience for both JavaScript and TypeScript.
In order to avoid bifurcating the linting tool space for TypeScript, we therefore plan to deprecate TSLint and focus our efforts instead on improving ESLint’s TypeScript support. Source: Palantir's blog
Starting April 28th, Codeac will switch the default TypeScript analysis to ESLint. We recommend moving forward with the modern ESLint approach. If you have already configured ESLint to support TypeScript in the standard way, Codeac will detect your .eslintrc automatically.
While the industry has moved toward ESLint, we will continue to support TSLint for legacy projects as a manual option in your .codeac.yml. If you have any issues with the migration or configuration, let us know, please. We will be happy to help you.