We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently prefer-to-have-count checks for 3 things within the expect call:
prefer-to-have-count
This rule should be specifically checking for the method .count() like the name describes. Currently it picks up other things like the following:
.count()
expect(await page.evaluate(() => { return document.querySelectorAll("*").length; })).toBe(10);
That sample above is incorrectly reported as an error since it matches all of the 3 conditions despite it not being a .toHaveCount() compatible call.
.toHaveCount()
Thank you! :)
The text was updated successfully, but these errors were encountered:
510e71c
🎉 This issue has been resolved in version 0.22.2 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Currently
prefer-to-have-count
checks for 3 things within the expect call:This rule should be specifically checking for the method
.count()
like the name describes. Currently it picks up other things like the following:That sample above is incorrectly reported as an error since it matches all of the 3 conditions despite it not being a
.toHaveCount()
compatible call.Thank you! :)
The text was updated successfully, but these errors were encountered: