Skip to content

New internal lint rule: use ESTree node ranges instead of TypeScript #4796

New issue
New issue
Closed as not planned
Closed as not planned
New internal lint rule: use ESTree node ranges instead of TypeScript#4796
Labels
accepting prsGo ahead, send a pull request that resolves this issuelocked due to agePlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.repo maintenancethings to do with maintenance of the repo, and not with code/docs
@JoshuaKGoldberg

Description

@JoshuaKGoldberg
JoshuaKGoldberg
opened on Apr 8, 2022

Overview

Following #4723 and #4790, it looks like we need to might need to always report fixer ranges using the ES tree nodes rather than TypeScript nodes. If that's the case (is it?) we should lint to make sure we don't accidentally use a TypeScript node.

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issuelocked due to agePlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.repo maintenancethings to do with maintenance of the repo, and not with code/docs

    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