Rules are not found in release `1.1.1`
See original GitHub issueWith my .eslintrc.js
file as follows:
module.exports = {
extends: [
'plugin:testing-library/react',
'plugin:jest-dom/recommended',
],
}
I am getting an error (for each rule) of
error Definition for rule 'XXX' was not found
where XXX
refers to all of the rules from this plugin (prefer-checked
, prefer-enable-disable
, and prefer-required
)
Downgrading my eslint-plugin-jest-dom
to version 1.1.0
fixes this issue and linting works as expected.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
java - Failed to execute goal org.apache.maven.plugins ...
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireMavenVersion failed with message: Detected Maven Version: 3.5.4 is not in the ...
Read more >Compose Material - Android Developers
Profile rules for a library are specified in a text file baseline-prof.txt located in the src/main or equivalent directory. The file specifies a...
Read more >App Store Review Guidelines - Apple Developer
The App Store Review Guidelines provide guidance and examples across a range of development topics, including user interface design, ...
Read more >Drools Expert User Guide
When not to use a Rule Engine. To quote a Drools mailing list regular: It seems to me that in the excitement of...
Read more >Release Strategy - OpenSSL
Releases that change the last digit, e.g. 1.1.0 vs. 1.1.1, can and are likely to contain new features, but in a way that...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Oops sorry. Picked the wrong name from the drop down. My apologies
Whoops, looks like I forgot to add the package name prefix to the rules in #4, sorry about that. I can confirm that this issue is fixed in 1.1.2, and I’ll make a fixed version of #4.