Skip to content

Move opinionated rules from 'eslint-recommended' to 'recommended'? #592

@borekb

Description

@borekb

While looking at #591, I encountered something that I wanted to discuss separately.

Intuitively, I would think that a typical config could look like this:

{
  extends: [
    // start from this
    'eslint:recommended',

    // disable rules that are incompatible with TS or better handled by it
    '@typescript-eslint/eslint-recommended',

    // turn on TS-specific recommended rules
    '@typescript-eslint/recommended'
  ]

However, @typescript-eslint/eslint-recommended already contains some opinionated rules so adding it to our config actually yielded some new errors, which I wouldn't have expected.

I think I'd prefer if eslint-recommended was just a compatibility config while all the additional, opinionated and possibly stricter rules were in recommended. What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpackage: 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

      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