-
Notifications
You must be signed in to change notification settings - Fork 150
feature request: no-await-fire-event #219
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
I guess this could be wrapped into a |
Works for me. My only thought would be that you wouldn't want the rules to conflict with each other for vue users but I'm not a vue user so that's not going to affect me. 🙂 |
I haven't thought about that conflict. Maybe we need to create this rule with a config options for disabling specific methods to be check so Vue users can enable this rule but disabling |
That would work. |
We accidentally enabled await-fire-event in our react project and discovered that awaiting fireEvent can actually cause tests to be slow and flaky as a result (removing the await fixes it). so was thinking that an opposite rule or even a config option to the await-fire-event to work in opposite mode would be useful
The text was updated successfully, but these errors were encountered: