-
Notifications
You must be signed in to change notification settings - Fork 148
await-async-events
doesn't seem to check calls from user sessions returned by userEvent.setup()
#812
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
Any estimate for this? We're about to start using this package in our project and this is a blocker for us. I'm using @testing-library/user-event 14.5.1 and eslint-plugin-testing-library 6.1.0. |
There is no ETA for this. PRs are more than welcome 🙂. |
Ok, I was already looking for a solution for that yesterday, I'll see if I can come up with something. |
I'd love to see this as well. Are there any more recent updates on this? Thanks, everyone! 😄 |
This makes me think I shouldn't be migrating my code to do: |
What rule do you want to change?
await-async-events
Does this change cause the rule to produce more or fewer warnings?
More warnings
How will the change be implemented?
The code needs to detect calls to
userEvent.setup()
and calls to the resulting object's methods.Example code
How does the current rule affect the code?
user.click()
and others returns aPromise
and should beawait
ed.How will the new rule affect the code?
Anything else?
see also #800
Do you want to submit a pull request to change the rule?
No
The text was updated successfully, but these errors were encountered: