Skip to content

Ban errorOnTypeScriptSyntacticAndSemanticIssues from being used within parser #8681

@bradzacher

Description

@bradzacher

Reference: import-js/eslint-plugin-import#2980

errorOnTypeScriptSyntacticAndSemanticIssues is an undocumented parser option.
Specifically it's an option that's documented and accepted in typescript-estree, but is not documented in parser.

It was never intended for use within eslint runs and it only works as a parserOption purely because we're lazy and we don't validate the options a user passes in.

We never wanted to report TS semantic errors from within our parser, and we have been building out syntax errors by hand within the conversion logic. As such we should outright ban this from being passed as a parserOption.

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issueenhancementNew feature or requestlocked due to agePlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.package: parserIssues related to @typescript-eslint/parser

    Type

    No type

    Projects

    No projects

    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