-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
🧹 Remove deprecated rules #140
Comments
Shall we make a milestone for the next major release and plan it for then? |
I think that would be good! Let me know what should be done for these kinda things and I will get on it 😁 |
It for sure has to be removed in a major version, so as soon as such PR is merged we are locked into shipping a new major And common practice is to let a deprecated rule stay for a minimum amount of releases / time with proper alerts, in case that’s done then feel free to create a PR that clears it up + if you can, create a milestone to track next major (the latter thing is a personal preference of mine, the main maintainers of this package may not agree, but I see no harm in doing it) |
That makes sense to me! no-hide-core-modules has been deprecated from v4.2.0 (61fcbb0) no-unsupported-features has been deprecated from v7.0.0 (58f3120) We're now on v16.3, I would hope that is enough time! 😂 |
Sounds like it’s very much time 😂 |
Based on this comment (mysticatea#69 (comment)) I think we should actually consider not removing the I can see both the use and validity of such problems. |
Both
n/no-hide-core-modules
andn/no-unsupported-features
are deprecated.We should probably look to remove those rules.
Participation
The text was updated successfully, but these errors were encountered: