-
Notifications
You must be signed in to change notification settings - Fork 227
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
[new rule] prefer .not.toHaveBeenCalled()
over toHaveBeenCalledTimes(0)
#1198
Comments
|
I'm not sure if enough of a clear gain here to make it worth having a whole new rule for this (the failure message is very similar, and it could be more consistent depending on the surrounding code), given you could use |
Reviving this as I'm seeing a lot of areas of this happening within a codebase - would be nice to have an autofixable rule here instead of flagging restricted syntax. |
The text was updated successfully, but these errors were encountered: