-
Notifications
You must be signed in to change notification settings - Fork 148
fix(prefer-screen-queries): take container into account #150
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
fix(prefer-screen-queries): take container into account #150
Conversation
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.
Hi Leandro and thanks for your PR! The fix itself looks fine. Could you add couple of examples using container to valid and invalid sections within rule doc?
@@ -4,9 +4,11 @@ import { ALL_QUERIES_COMBINATIONS } from '../../../lib/utils'; | |||
|
|||
const ruleTester = createRuleTester(); | |||
|
|||
const ALL_QUERIES_COMBINATIONS_PLUS_CONTAINER = [...ALL_QUERIES_COMBINATIONS, 'container'] |
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 think that it would be better to keep ALL_QUERIES_COMBINATIONS
and then use container for its specific scenarios. As this would test as valid scenarios that do not match real tests. For instance, in the line 12 it would translate to
screen.container()
which is not RTL valid code. Same below for
within(component).container()
Thank you for the PR! I added a couple of small comments 😄 |
Co-authored-by: Gonzalo D'Elia <[email protected]>
🎉 This PR is included in version 3.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@all-contributors please add @lourenci for bug, code and test |
I've put up a pull request to add @lourenci! 🎉 |
…ing-library#150)" This reverts commit a783036.
It fixes #149.