Rule proposal: Warn when deprecated APIs are used (eslint-plugin-deprecation) #8988
Open
6 tasks done
Labels
enhancement: new plugin rule
New rule request for eslint-plugin
package: eslint-plugin
Issues related to @typescript-eslint/eslint-plugin
triage
Waiting for maintainers to take a look
Before You File a Proposal Please Confirm You Have Done The Following...
My proposal is suitable for this project
Description
Re-opening #1223: being able to lint against usage of an API marked as
@deprecated
is a common request for TypeScript developers. It was a TSLint rule back in those days, and now is provided primarily by https://github.com/gund/eslint-plugin-deprecation.eslint-plugin-deprecation
existing is why #1223 was closed by a docs change pointing folks externally.But! Since then:
eslint-plugin-deprecation
isn't 100% actively maintained, and has an issue template notice indicating its maintainer doesn't have the bandwidth to ramp up on it & actively fix issuesProposal: let's write a new implementation of a
deprecation
rule in this repo?Fail Cases
Pass Cases
Additional Info
Note that the licensing here is tricky. https://github.com/gund/eslint-plugin-deprecation includes the following README.md note:
...and is licensed under the GNU Lesser General Public License.
We need to be very sure that if this issue is accepted, any code added to our project is not based on the GNU license, and is at most licensed under MIT. If this is accepted, I think a member of the typescript-eslint team should work on it.
Other references of related licensed rules are:
cc @gund - you've done a great job for a while of keeping
eslint-plugin-deprecation
afloat ❤️. If you have any thoughts here, that'd be great.The text was updated successfully, but these errors were encountered: