-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added specific eslint rules for typescript tests #2634
Conversation
'@typescript-eslint/no-throw-literal': off | ||
'@typescript-eslint/require-await': off | ||
'@typescript-eslint/await-thenable': off | ||
'prefer-promise-reject-errors': 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also please use off
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'@typescript-eslint/require-await': off | ||
'@typescript-eslint/await-thenable': off | ||
'prefer-promise-reject-errors': 0 | ||
'no-new-wrappers': 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are standard ESLint rules so they should work on both Flow and TS.
Can you please give an example of why you disabled them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of the tests are creating wrapped instances of primitives (for example - isCollection-test.js
).
At the moment it has // eslint-disable-next-line no-new-wrappers
set on those lines, but isn't it better to disable it on a global level? there are multiple places that does that.
@IvanGoncharov ping :) |
Extracted from: #2609
@IvanGoncharov