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
What should we do in the new major #574
Comments
My only ambition for a major would be the recommended ruleset update 🙃 (but as posted over there in the relevant issue, I'd prefer to add like a billion things to it so.... 😅 ) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just making this meta issue to consolidate what we'd like to land in/around the new major, since we've made some comments in different places:
Depending on time, we could try to do #482.
(I don't think we're in any major rush, since we're not actually blocking anything re jest 26 or eslint 7 - I could be wrong there?)
@SimenB made some comments too:
toStrictEqual
- personally I'm happy with that remaining an autofix, because running your tests should tell you if it's actually changed a behaviour (which is also why I wondered if maybe it should be recommended - it strikes me as a bit like==
vs===
?)no-test-callback
should use a suggestion as it's dangerous to autofixno-test-callback
tono-done-callback
as it's a more accurate name (👍)The text was updated successfully, but these errors were encountered: