You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One to make sure that expect awaits if locators are what is being asserted on, and one to make sure there are no useless awaits. That being said you can still do the following
no-floating-promises requires type information, which I very explicitly try to avoid recommending. Not because those are bad rules, but because I want a great linting experience regardless of if you have rules like no-floating-promises or not.
Right now there are two
await
related rulesOne to make sure that
expect
awaits if locators are what is being asserted on, and one to make sure there are no uselessawaits
. That being said you can still do the followingWhen you should have to use an
await
onlocator.click()
.It would be nice to have a rule to assert that all action driven functions also need an await call.
Alternatively, I'm open to other eslint rules that may already handle this case. I've tried a few but none of them seem to catch this use case.
The text was updated successfully, but these errors were encountered: