Skip to content

Create a "strict" config between "recommended-requiring-type-checking" and "all" #4648

Closed
@JoshuaKGoldberg

Description

@JoshuaKGoldberg

Overview

Moving discussion out of https://twitter.com/JoshuaKGoldberg/status/1500610010576994306: it seems to me that there are at least two classifications of lint users we should target:

  • Starter: most users at least to begin with. These users likely don't have a "power user" w.r.t. typescript-eslint on their project and thus don't want particularly strict, annoying options enabled. They should be given rules that are clearly demonstrate linting value.
    • Lint configuration target today: recommended or recommend-requiring-type-checking
  • Power: users who have seen the power of typed linting and want to get the most out of it. They want our somewhat-opinionated strict configs that enforce best practices too -- and can handle the sometimes aggressive lint errors as a result.
    • Lint configuration target today: missing

I propose we create a plugin:@typescript-eslint/strict config that adds a suite of best practice rules on top of recommended-requiring-type-checking.

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issuepackage: eslint-pluginIssues related to @typescript-eslint/eslint-pluginrecommended-rulesDiscussion about recommended rule sets

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions