Fix eslint-plugin-jest config #15826
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
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/54989/ |
liuxingbaoyu
approved these changes
Aug 2, 2023
nicolo-ribaudo
approved these changes
Aug 2, 2023
github-actions
bot
added
the
outdated
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
eslint-plugin-jestrules have been disabled after #15748In this PR we extend the
filesandrulesonly when the eslint config item, returned byjest:recommended, has configured such key.I realize that the eslint-plugin-jest is not activated after I delete a few plugin-jest rules and it turns out the linter is still green: It's simply too good to be true. My guess is that if we blindly extend empty rules, the jest rules are not enabled.
Then I enable the
jest/no-identical-titlerule to prove that the linter is working again.