-
Notifications
You must be signed in to change notification settings - Fork 144
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
feat: new no-unnecessary-act
rule
#365
Conversation
5c4bb45
to
a7996e6
Compare
isNodeComingFromTestingLibrary wasn't checking if the imported declaration name matches some Testing Library valid module
44a7d6a
to
489be04
Compare
} | ||
); | ||
|
||
const isReactDomTestUtilsAct = (() => { |
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 know there are several IIFE used here and some blocks could be refactored or extracted. I'm gonna leave it like this so first I fix the issues found and then, having proper context, I'll refactor and extract corresponding functions.
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 don't know enough about this plugin to provide very valuable feedback on the code, but here's one bit of feedback on the docs
Other than that, this looks great! |
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.
This looks great. I left some minor suggestions, but LGTM. Kudos to @alessbell and @Belco90 ! 🚀
🎉 This PR is included in version 4.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Closes #259
Co-authored-by: @alessbell
I've found few issues detecting Testing Library packages during the development of this rule. I've fixed one of them, and I'll pinpoint the rest of them in this very PR so I can fix them separately after this rule gets merged.