-
Notifications
You must be signed in to change notification settings - Fork 1.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
prevent test.only #24235
prevent test.only #24235
Conversation
"plugins": [ | ||
"@typescript-eslint", | ||
"no-only-tests" | ||
], |
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.
I had #24161 with
"mocha/no-exclusive-tests": "error"
Is the one mentioned in this PR more general? I don't know which one is necessarily better/ more broader.
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.
as long as it works in the python ext correctly, we should probably use yours if it matches with what vscode is doing
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.
vscode had something like
"local/code-no-test-only": "error",
but I couldnt figure out where the part ""local/code" was coming from, and just saw/tested with mocha/no-execlusive-tests works. I think we can still use your no-only-tests though. For me that looks more generalized/better since we seem to have combination of different tests in Python repo.
I almost checked in a change to disable all tests again. This will prevent that