Skip to content

⚡️ Performance: Use a dedicated quick JSDoc parser for no-deprecated #9858

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

Open
JoshuaKGoldberg opened this issue Aug 21, 2024 · 0 comments
Labels
enhancement New feature or request package: eslint-plugin Issues related to @typescript-eslint/eslint-plugin performance Issues regarding performance team assigned A member of the typescript-eslint team should work on this.

Comments

@JoshuaKGoldberg
Copy link
Member

Overview

Following #7997 -> #9783 (comment) -> #9857: we'd like to not have a dependency on TypeScript's full JSDoc parsing. But at least our no-deprecated rule relies on it, as does the older community deprecated/deprecated. That means #9857 is blocked until at least ours can no longer use TypeScript's JSDoc parsing.

Instead, we'd like to write a separate, small, quick JSDoc parser utility. It could just look for @deprecated on a node & parse out any deprecation reason(s) as text. There's no need for it to look for other tags or get any more rich info.

💖

@JoshuaKGoldberg JoshuaKGoldberg added enhancement New feature or request package: eslint-plugin Issues related to @typescript-eslint/eslint-plugin performance Issues regarding performance team assigned A member of the typescript-eslint team should work on this. labels Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request package: eslint-plugin Issues related to @typescript-eslint/eslint-plugin performance Issues regarding performance team assigned A member of the typescript-eslint team should work on this.
Projects
None yet
Development

No branches or pull requests

1 participant