-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Closed
Labels
bugSomething isn't workingSomething isn't workingpackage: eslint-pluginIssues related to @typescript-eslint/eslint-pluginIssues related to @typescript-eslint/eslint-pluginscope analyserIssues that are caused by bugs/incomplete cases in the scope analyserIssues that are caused by bugs/incomplete cases in the scope analyser
Milestone
Description
Actual Result
$ TIMING=true eslint ./ --ext ts,tsx
Rule | Time (ms) | Relative
:------------------------------------------------|----------:|--------:
@typescript-eslint/no-unused-vars-experimental | 4193.923 | 56.4%
@typescript-eslint/no-misused-promises | 1047.652 | 14.1%
@typescript-eslint/restrict-template-expressions | 796.963 | 10.7%
react/destructuring-assignment | 261.669 | 3.5%
react/void-dom-elements-no-children | 136.631 | 1.8%
@typescript-eslint/no-unnecessary-condition | 123.065 | 1.7%
@typescript-eslint/require-await | 120.714 | 1.6%
@typescript-eslint/no-unnecessary-type-assertion | 85.675 | 1.2%
@typescript-eslint/camelcase | 48.977 | 0.7%
unicorn/prefer-string-slice | 46.659 | 0.6%
Expected Result
I'm surprised that the rule represent more than half of time. Is it something known or some special check that makes it more consuming than other rules?
Versions
| package | version |
|---|---|
@typescript-eslint/eslint-plugin |
2.11.0 |
@typescript-eslint/parser |
2.11.0 |
TypeScript |
3.6.4 |
ESLint |
6.7.2 |
node |
13.2.0 |
yarn |
1.19.2 |
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingpackage: eslint-pluginIssues related to @typescript-eslint/eslint-pluginIssues related to @typescript-eslint/eslint-pluginscope analyserIssues that are caused by bugs/incomplete cases in the scope analyserIssues that are caused by bugs/incomplete cases in the scope analyser