-
Notifications
You must be signed in to change notification settings - Fork 147
feat(prefer-find-by): report presence assertions #450
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(prefer-find-by): report presence assertions #450
Conversation
@zaicevas oh wow, it seems complex indeed! I'll try to take a look at the end of the week, thanks ✨ |
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.
It looks great in general! I just requested an additional test.
The implementation to detect the waitFor
+ presence/absence assertion seems a bit brittle since it's too tight to a particular tree. But I guess this is what it is, right?
I'm surprised the auto-fix works for this new invalid usage reported 😮
Yeah :S I guess one can't escape that.
Yep, that's because it relies on a few variables (such as I've noticed github actions are failing because of what seems to be unrelated reasons. Would you mind helping with that? |
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.
All good from my side. Thanks again!
🎉 This PR is included in version 4.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Checks
Changes
prefer-find-by
by reporting presence assertionsContext
Closes #420
Not gonna lie, took much more effort and AST parsing than I initially thought 😄