-
Notifications
You must be signed in to change notification settings - Fork 236
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: create no-deprecated-functions
#560
Conversation
b00f769
to
40c0394
Compare
40c0394
to
73a5d36
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't reviewed the rule itself, but yeah the concept and it being recommended seems good to me. Also I believe there were a couple of rules I wanted to make recommended last time I worked on eslint-plugin-jest, I hope I documented it in code comments or so, just in case you come across it make sure to enable them as well 😅 (on mobile atm) |
Can make https://github.com/jest-community/eslint-plugin-jest/blob/master/docs/rules/no-jasmine-globals.md recommended as well. Not sure what others you may have wanted 😀 |
@SimenB I thought |
Yeah, let's hope so 😀 |
da89a11
to
0ce9b84
Compare
But you suggested documenting them as being scheduled for removal in Jest 26? Was that intentional? |
Oh... Nope, Jest 27 😀 |
0ce9b84
to
612231a
Compare
612231a
to
b63c43e
Compare
Are there plans to ever deprecate the aliases matchers in |
Good point, we could do that. I'm not sure about how much usage they get, might be controversial |
We can but see 🤷 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add to main readme and I think we're good to go?
Oh yeah good point - I really should port the readme table generator script I wrote for |
👍 to more automation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome 👍 I'd add it to recommended
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 I like it.
I agree this would be fantastic as a codemod. We don't use jest['x']
anywhere.
@G-Rath another one: jestjs/jest#9962. We can probably remove the old one in 27, but let's just say |
|
😀 |
207f1e2
to
ac8f641
Compare
I edited 2 hours before you commented 😉 |
Yes, but you forgot to edit the notification email in my inbox 😉 |
Thanks @G-Rath! Thoughts on a new major adding this rule to the recommended set and dropping Node 8? |
# [23.9.0](v23.8.2...v23.9.0) (2020-05-04) ### Features * create `no-deprecated-functions` ([#560](#560)) ([55d0504](55d0504))
🎉 This PR is included in version 23.9.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
A bit surprised to already get warnings for |
Ergh, didn't think about that case... Yes, a release is coming today or tomorrow. Might need an option for folks who haven't upgraded yet? I think it makes sense regardless of this issue for people to be able to specify their Jest version, like react: https://github.com/yannickcr/eslint-plugin-react/blob/master/README.md#configuration |
Tracked by #561 - I'll implement it tomorrow morning :) (NZT, so that's ~8-9 hours from now) |
Thanks @G-Rath! |
We might wanna release a patch skipping |
I've done for the simple route - hopefully jest won't have any big deprecations, but if so we can refactor.
closes #559
/cc @cpojer - this should do as a codemod, tho I'm curious on if Facebook have any
x["y"]
syntax in your codebase 🤔