-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
expect.extend creation of asymmetric matchers not mentioned in documentation #9060
Comments
I was going to log an issue for this, but I think this one is related... There doesn't seem to be documentation around how to create asymmetric matchers that is relevant or up to date (maybe?). |
Docs PRs are always most welcome 😀 Seems we've forgotten to document this one |
Ok, I will make a pull request |
Every custom matcher that is supplied to expect.extend is available as an asymmetric matcher, although one that returns the result asynchronously should not be used. If you are using typescript you can do the following ( instead of using Matchers<R,T> )
|
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🐛 Bug Report
To Reproduce
There is no mention in the documentation of the behaviour described.
Expected behavior
I expect it to be described so the functionality created can be used.
#6649
I am happy to update the documentation if required.
The text was updated successfully, but these errors were encountered: