Suggestion: add a code linter
Opened this issue · 1 comments
Deleted user commented
Why a linter is necessary
As this project evolves, it’s inevitable that there will be bugs introduced that the TypeScript compiler simply isn’t designed to detect. A linter such as ESLint, with the help of the TypeScript ESLint parser, can detect issues like stringifying an object, forgetting to handle promise rejections, or misusing any (which is, frankly, defeats the purpose of using TypeScript and is an accident waiting to happen). It can also enforce stylistic decisions, like consistent privacy modifiers on classes and the usage of namespaces.
TSLint vs ESLint
While the TSLint linter is clearly designed for TypeScript, it has been deprecated and superseded by ESLint with the typescript-eslint parser. I would recommend using ESLint.