Add notice instead of logging missing rules for external code analyzer #315
Labels
status: accepting prs
Please, send in a PR to resolve this! ✨
type: enhancement
New feature or request
🚀 Feature Request
Following #151 example, if you try to convert TSLint rules into ESLint ones for some projects that make use of external static code analyzer like as Elm language client VSCode, you will see a long
tslint-to-eslint-config.log
file whose content is the following:As you can check at the source code, the tslint.json extends from
tslint-sonarts
, which is another static code analyzer for Typescript. The rule list can be found at readme at SonarTS repo.Existing Behavior
The above log file is being generated with tons of rules that are not supported by ESLint.
Change Proposal
Provide a notice which states external code analyzer are not supported by ESLint.
I am not sure if this should be of concern but I had to bring int into discussion.
Cheers!
The text was updated successfully, but these errors were encountered: