-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Data: Fix no-node-access
violation in suspense tests
#46657
Conversation
Size Change: 0 B Total Size: 1.32 MB ℹ️ View Unchanged
|
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.
The lint rule thinks that this.props
is a DOM element whose .children
field is being accessed?
1157802
to
f409a1c
Compare
Yes 😅 A false positive. I think it was fixed in the newer versions of |
What?
This PR fixes a
no-node-access
violation in the suspense tests.Why?
This is a preparatory PR in order tobe able to enable the
no-node-access
ESLint rule for all tests.How?
We're just changing the way we access the
children
prop to avoid the false positive.Testing Instructions
Verify tests still pass:
npm run test:unit packages/data/src/components/use-select/test/suspense.js