-
-
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
[Feature]: remove alised matchers #13164
Comments
Yeah, this should be fine to do for v30 👍 |
Hi, I would like to do this issue, can I? And this matchers will be completely removed, right? Or just show a warning like |
Thanks! Feel free to send a PR, but note that it won't be merged for some months 🙂 It'll land eventually, tho 😀 And yes, just remove it. We have a lint rule ( |
Have opened DefinitelyTyped/DefinitelyTyped#67143 marking the matchers as deprecated |
…Rath * fix: mark alias matchers as deprecated jestjs/jest#13164 * chore: remove trailing space * test(jest): add uses of deprecated matchers * chore(jest): double quotes not single quotes
In case someone wants a quick way to replace deprecated matchers in their tests, I've created a config file for a tool called |
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. |
🚀 Feature Proposal
From jest-community/eslint-plugin-jest#1210 (comment)
Let's axe the following matchers:
in favor of their native counterparts:
Motivation
no-alias-methods
provides a migration method, which can be automatically fixedeslint-plugin-jest
) shave off a little complexity i.e. by not having to check for two matchersExample
No response
Pitch
Because the matchers are in the jest core.
The text was updated successfully, but these errors were encountered: