-
Notifications
You must be signed in to change notification settings - Fork 238
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
"all" config includes deprecated rules #663
Comments
Yeah, they were supposed to go away, we just forgot 😅
That might make sense regardless of them being removed in the next major or not. @G-Rath thoughts? |
Let's not forget to remove deprecated rules in future majors 😅 Also, I think this sets a predicents we should be careful of, as it's arguably breaking a similar but more subtle way to us removing the deprecated rules in a minor. I've made a PR for this :) |
We explicitly say |
🎉 This issue has been resolved in version 24.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Cheers fellas! |
I think I just missed the boat for a major release, but I just wanted to clarify how deprecated rules are handled in this plugin.
Currently the "all" config includes all rules in the
rules
directory, including deprecated rules that still exist in the source code.I thought that those deprecated rules might get removed in the next major release. Is that generally the case, or are they expected to remain indefinitely?
Would it make sense for
allRules
to filter onrule.meta.deprecated
?The text was updated successfully, but these errors were encountered: