typescript-eslint recommended rules

[bartlomieju]

Tracking issues for recommended rules of typescript-eslint

https://github.com/typescript-eslint/typescript-eslint/blob/v3.1.0/packages/eslint-plugin/src/configs/recommended.ts

• adjacent-overload-signatures (easy)
• ban-ts-comment
• ban-types
• explicit-module-boundary-types (easy)
• no-array-constructor
• no-empty-function (needs to be fixed, false positives for constructors)
• no-empty-interface
• no-explicit-any
• no-extra-non-null-assertion
• no-extra-semi (easy)
• no-inferrable-types (easy)
• no-misused-new
• no-namespace
• no-non-null-asserted-optional-chain
• no-non-null-assertion
• no-this-alias
• no-unused-vars (hard, needs scope analysis)
• no-var-requires
• prefer-as-const
• prefer-namespace-keyword
• triple-slash-reference

[lucacasonato]

I don't think no-var-requires makes sense for us: https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/no-var-requires.md

[bartlomieju]

I've marked this issue with 0.2.0 milestone. I want to implement remaining rules this week so they will be included in deno v1.1

[disizali]

@bartlomieju
i'm almost done with no-this-alias and ban-ts-comment,
Also no-inferrable-types is my next goal.
you can start the rest first.

[iykekings]

I'm working on no-non-null-asserted-optional-chain and no-non-null-assertion.

[bartlomieju]

@iykekings are you still working on no-non-null-asserted-optional-chain?

[iykekings]

Yes, had plenty on my plate at work. I will try to finish it ASAP

[magurotuna]

I'm working on adjacent-overload-signatures.

[magurotuna]

I'll take no-inferrable-types next.

[akshatagarwl]

@bartlomieju It seems no-inferrable-types is done. It's not updated in your comment

[notfilippo]

Taking explicit-module-boundary-types 😄