You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@G-Rath Looks like no-try-expect is still in the recommended list (v24 major was released recently).
I got here because I'm using eslint-find-rules to find deprecated rules in my configs and it failed for jest/recommended.
I'm assuming the recommended property needs to be removed from the rule file.
But also thinking if this can be prevented in the future.
Although if we deprecate a rule and still keep it in the jest/recommended, then I'm not sure how.
@alexilyaev this is because we forgot to remove the deprecated rules in the new major.
We can't change what's in recommended without a new major, so while we addresses this for all when it was reported, we can't do anything in this case without technically breaking semver.
I understand that.
But ideally there would be an automated process to check for such a thing, to alleviate the need to not forget to remove rules from all and recommended.
Or at least a formal manual step-by-step guide for major releases, noting the necessary things to go through.
To continue #648
@G-Rath Looks like no-try-expect is still in the
recommended
list (v24 major was released recently).I got here because I'm using eslint-find-rules to find deprecated rules in my configs and it failed for
jest/recommended
.I'm assuming the
recommended
property needs to be removed from the rule file.But also thinking if this can be prevented in the future.
Although if we deprecate a rule and still keep it in the
jest/recommended
, then I'm not sure how.Any way, here's how I ran
eslint-find-rules
:The text was updated successfully, but these errors were encountered: