New rule: no-exclusive-tests #12
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jun 18, 2019
|
This one is good to merge once #11 has been merged (and following a rebase from |
textbook
force-pushed
the
no-exclusive-tests
branch
2 times, most recently
from
8de49f4
to
86e7501
Compare
|
@textbook a couple of conflicts to resolve and we're good to go! 👌 |
textbook
force-pushed
the
no-exclusive-tests
branch
from
86e7501
to
ef53e66
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Name and report based on the Mocha ESLint plugin's
no-exclusive-testsrule.Can detect and fix
Scenario.only.