-
Notifications
You must be signed in to change notification settings - Fork 40
jest-dom/prefer-empty wrong detection, and wrong fix. #61
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
Comments
🎉 This issue has been resolved in version 3.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@all-contributors please add @RIP21 for bugs |
I've put up a pull request to add @RIP21! 🎉 |
@RIP21 I believe all of the issues you reported should be fixed now. Mind confirming in the latest release? Much appreciation for the issues you reported and all the great examples, I was able to use them for the tests... |
@benmonro awesome. Thank you very much! You're legend :) I'll update on Monday and see how it goes :) |
@benmonro I'm afraid this is not fully fixed. Template strings are not properly handled.
Still pops up as an error |
@atsikov thank you for reporting, I hadn't considered that use case. will have a fix published shortly |
@atsikov fix released in 3.1.6 can you please update and let me know if it fixes your issue and/or any other issues I may have missed? many thanks -Ben |
Wow @benmonro that was fast! 🚀 However it still shows an error in case template doesn't have params.
|
ah yeah ok that actually might take a bit more work, will have to look at that tonight, as a work around you can use |
@atsikov sorry for the delay, 3.1.7 should address your issue, but please do let me know if you find another! |
eslint-plugin-jest-dom
version: 3.0.1node
version: 12.16.1npm
version: 6.13.4Broken fix and detection
This is detected as error
Fixes to
The text was updated successfully, but these errors were encountered: