Skip to content

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

@JoshuaKGoldberg

Description

@JoshuaKGoldberg

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.

💖

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpackage: eslint-pluginIssues related to @typescript-eslint/eslint-pluginperformanceIssues regarding performanceteam assignedA member of the typescript-eslint team should work on this.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy