Open fea17e86 opened 5 years ago
When ESLint has feature parity with TSLint, TNS should migrate completely to ESLint with a breaking version change.
Additionally, documentation should be added to help people migrate from TSLint to ESLint, or an auto-tool can be included to aid in migration.
References:
:+1: on this. Most of my TypeScript projects now use ESLint. Noticed that this generator is still using TSLint when I ran it today.
When ESLint has feature parity with TSLint, TNS should migrate completely to ESLint with a breaking version change.
Additionally, documentation should be added to help people migrate from TSLint to ESLint, or an auto-tool can be included to aid in migration.
References: