-
Notifications
You must be signed in to change notification settings - Fork 155
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
[tests-only] override lint rules for tests/e2e #10562
Conversation
05ebd82
to
2c51001
Compare
"@typescript-eslint/no-unsafe-assignment": "off", | ||
"@typescript-eslint/no-explicit-any": "off", | ||
"@typescript-eslint/no-unsafe-member-access": "off", | ||
"@typescript-eslint/no-unsafe-argument": "off", | ||
"@typescript-eslint/no-unsafe-call": "off", | ||
"@typescript-eslint/no-unsafe-return": "off", | ||
"@typescript-eslint/restrict-template-expressions": "off", | ||
"@typescript-eslint/restrict-plus-operands": "off", | ||
"@typescript-eslint/no-unnecessary-type-assertion": "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.
we will eventually change them to error
if possible but in separate PRs because the changes would be large
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.
hmm, couldn't think of anything on what to put in the docs. any idea? |
something like: |
done. added the docs |
Quality Gate passedIssues Measures |
* tests(e2e): use separate eslint config for tests * tests(e2e): fix step args * docs: add e2e lint section
Description
To prevent mistakes like see here #10553 (which caused tests to be flaky), I have implemented override config for e2e tests with customized rules for
tests/e2e
. With this, we can have separate rules defined for the e2e test code.Related Issue
Motivation and Context
How Has This Been Tested?
Types of changes