-
Notifications
You must be signed in to change notification settings - Fork 147
RFC: fixer for wait
(V7)
#86
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
This seems really interesting! I guess the rule could be called something like I'll give it a try tomorrow. |
@Belco90 yep that should work, see the updated astexplorer for an implementation of the rule |
This will be released on v3 |
feat(await-async-utils): reflect waitFor changes (#89) feat: new rule no-wait-for-empty-callback (#94) feat: new rule prefer-wait-for (#88) feat: new rule prefer-screen-queries (#99) BREAKING CHANGE: drop support for node v8. Min version allowed is node v10.12 (#96) BREAKING CHANGE: rule `no-get-by-for-checking-element-not-present` removed in favor of new rule `prefer-presence-queries` (#98) Closes #85 Closes #86 Closes #90 Closes #92 Closes #95 Co-authored-by: timdeschryver <[email protected]>
🎉 This issue has been resolved in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Would it be an option to add a fixable rule for the changes made to
wait
?The implementation could look like this
input:
output:
The text was updated successfully, but these errors were encountered: