eslint-plugin-deprecation
eslint-plugin-deprecation copied to clipboard
gund
ESLint rule that reports usage of deprecated code
```ts type T = { new?: string; /** @deprecated */ old?: string; }; const myT: T = { // I'd expcect an ESLint warning here, but there is none old:...
In a rather large project, that unfortunately I'm not at liberty to share, performance of this plugin is a bit dissappointing. The result of this is not only that it...
In the following scenario, when calling `method()` on an instance of the `New` class, the plugin should not report an error, but it does: ```typescript class Old { /** @deprecated...
Hi, with the following setting > "deprecation/deprecation": "warn" I get warnings from my barrel (index.ts) Like this ```bash ~\Repos\akita\libs\akita\src\lib\index.ts 4:10 warning 'arrayAdd' is deprecated. deprecation/deprecation ``` But it's not using...
Usages of the chrome API, defined in this types - https://www.npmjs.com/package/@types/chrome, cause deprecation errors. E.g. the following code ```ts chrome.tabs.query({}); ``` leads to this error: ```bash deprecation_chrome/index.ts 1:1 error 'chrome'...
Currently, using [`[email protected]`](https://github.com/eslint/eslint/releases/tag/v9.0.0-alpha.0), `eslint-plugin-deprecation` fails with the following error: ``` An unexpected error occurred: TypeError: context.getAncestors is not a function Occurred while linting /Users/k/p/project/eslint.config.js:1 Rule: "deprecation/deprecation" at getParent (/Users/k/p/project/node_modules/eslint-plugin-deprecation/dist/rules/deprecation.js:86:31) at...
Add support for ESLint v9 while maintaining backwards compatibility with all previously supported ESLint versions. Closes #78 This PR is cannot be finished until: - [x] Library is migrated to...
I noticed that this plugin does not warn for usage of deprecated jsx props. Since we needed this, I've written this plugin: https://github.com/sebakerckhof/eslint-plugin-deprecated-jsx-props I originally started with bringing https://github.com/Drawbotics/eslint-plugin-deprecated-props up...
I noticed this more or less accidentally - if you e.g. have code like this: ```ts interface MyInterface { /** * This is old! * @deprecated Do not use this...
The second required disable comment shouldn't be needed/the lint error is reported incorrectly. ````ts function demo( options: { /** * @deprecated */ deprecated?: boolean; replacement?: boolean; } = {} ):...
