Skip to content
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

feat(jest): fail if more than expected matcher arguments are passed #199

Merged
merged 3 commits into from
Jan 1, 2024

Conversation

m-radzikowski
Copy link
Owner

Prevents accidental calling toHaveReceivedCommand(Cmd, {}) instead of toHaveReceivedCommandWith(Cmd, {})

Closes #191

Jest now includes own types in @jest/globals packages.
Use it for custom Jest matchers types.
Add declaration exposing custom matchers
in the "expect" library types.

Fixes #180
Prevents accidental calling toHaveReceivedCommand(Cmd, {})
instead of toHaveReceivedCommandWith(Cmd, {})

Closes #191
Base automatically changed from issue180 to main January 1, 2024 21:19
@m-radzikowski m-radzikowski merged commit 6f7bb59 into main Jan 1, 2024
2 checks passed
@m-radzikowski m-radzikowski deleted the issue191 branch January 1, 2024 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

toHaveReceivedCommand should throw an error if it receives a second parameter.
1 participant