Remove eslint-plugin-deprecation
#59
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type
Description
eslint-plugin-deprecationis now in maintenance mode and its functionality has been moved to an equivalenttypescript-eslintrule. Enabling this plugin in v9 of ESLint throws an error because the plugin requires type information to work properly.Furthermore, it seems as though
eslint-plugin-deprecationalways required type information to work properly, but we never had type information enabled and it seems like it wasn't being enforced by ESLint prior to v9.Given we do NOT want to enable type information for ESLint, I am removing the rule from our templates.
Related