Tracking issue: ESLint recommended rules

[Stupremee]

Tracking issue for rules from eslint:recommended set.

• constructor-super
• for-direction
• getter-return
• no-async-promise-executor
• no-case-declarations
• no-class-assign (blocked on scope analysis)
• no-compare-neg-zero
• no-cond-assign
• no-const-assign (blocked on scope analysis)
• no-constant-condition
• no-control-regex
• no-debugger
• no-delete-var
• no-dupe-args
• no-dupe-class-members
• no-dupe-else-if
• no-dupe-keys
• no-duplicate-case
• no-empty
• no-empty-character-class
• no-empty-pattern
• no-ex-assign (blocked on scope analysis)
• no-extra-boolean-cast
• no-extra-semi
• no-fallthrough (blocked on code flow analysis)
• no-func-assign (blocked on scope analysis)
• no-global-assign (blocked on scope analysis)
• no-import-assign (blocked on scope analysis)
• no-inner-declarations
• no-invalid-regexp
• no-irregular-whitespace
• no-misleading-character-class
• no-mixed-spaces-and-tabs
• no-new-symbol
• no-obj-calls
• no-octal
• no-prototype-builtins
• no-redeclare (blocked on scope analysis)
• no-regex-spaces
• no-self-assign
• no-setter-return
• no-shadow-restriced-names
• no-sparse-arrays
• no-this-before-super
• no-undef (blocked on scope analysis)
• no-unexpected-multiline
• no-unreachable (blocked on code flow analysis)
• no-unsafe-finally
• no-unsafe-negation
• no-unused-labels
• no-unused-vars (blocked on scope analysis)
• no-useless-escape
• no-with
• require-yield
• use-isnan
• valid-typeof

[finn-orsini]

@Stupremee - I'm interested in picking some of these up if you're open to contributions here. If so, is it better if I create an issue for each rule I pick up, or link PRs to this tracking issue?

[Stupremee]

Yes, we are open to contributions!
It's fine if you just link this tracking issue.
For example contributions of new rules, you can look at some older PRs that add new rules, like #89.