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
Looks like a similar issue was referenced here: #219. In our case, expect in a finally without a return does not cause an ESLint issue.
expect
finally
describe("making a network call", () => { it("Makes the correct call", () => { const mySpy = jest.fn(); const callMySpyAsync = () => Promise.resolve().then(() => mySpy(5678)); callMySpyAsync(1234).finally(() => { expect(mySpy).toHaveBeenCalledWith(1234); }); }); });
The text was updated successfully, but these errors were encountered:
🎉 This issue has been resolved in version 24.4.3 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
🎉 This issue has been resolved in version 25.0.0-next.5 🎉
G-Rath
Successfully merging a pull request may close this issue.
Looks like a similar issue was referenced here: #219. In our case,
expect
in afinally
without a return does not cause an ESLint issue.The text was updated successfully, but these errors were encountered: