-
Notifications
You must be signed in to change notification settings - Fork 150
new rule: no-container #171
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
Hi, everyone! I'd like to help implementing this rule, could I be assigned to it @nickmccurdy ? |
Sure, it's all yours 😄 You might want to review #165 as well because there were some mentions about this ticket. |
Thanks @gndelia ! |
🎉 This issue has been resolved in version 4.0.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Inspiration: Using container to query for elements
This would error on
container
methods likequerySelector
that are often used instead of get/query functions, as there might be other reasons why you'd need to access the container in a test (such as assertions). It would be nice to give suggestions of specific get/query functions as well, but I'm not sure how far we could get.The text was updated successfully, but these errors were encountered: