-
Notifications
You must be signed in to change notification settings - Fork 13
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
Replace etc/no-deprecated
with eslint-plugin-deprecation
#732
Comments
Or with |
What's the benefits over https://github.com/import-js/eslint-plugin-import/blob/HEAD/docs/rules/no-deprecated.md ? (Reference voxpelli/eslint-config#160) |
Just tested the rules on a real-world codebase:
So Created #739 to disable |
Right, makes sense, type resolutions can be more complex What are the two warnings that differ between the 78 and 76 ones? |
@voxpelli Seems like
Also tested time difference:
|
Yikes, yeah, these rules can be really slow, I tried adding deprecation checks to a large monorepo at a recent job and it increased the execution time of the linting so much that I reverted on it before ever suggesting the change 😕 |
So which one of these is recommended to use lol? |
@DeadlyMissile I considered migrating away from But functionality-wise, all three are the same. |
Sorry to add to an old issue @EvgenyOrekhov, but it seems to break with Typescript 5.2, see cartant/eslint-plugin-etc#64 |
https://github.com/gund/eslint-plugin-deprecation
Unless cartant/eslint-plugin-etc#53 gets fixed.
The text was updated successfully, but these errors were encountered: