Skip to content

Configs: Allow strict configs to have more strict options than recommended? #7318

@JoshuaKGoldberg

Description

@JoshuaKGoldberg

Before You File a Proposal Please Confirm You Have Done The Following...

Description

Coming over from comment thread #7110 (comment): rules are occasionally in a situation where:

  • Many users in the recommended configs don't want to use their full options, as they're more "strict" than common use cases
  • We still want to enable the strict options for users, especially those on the strict configs

What if we added to the defaultOptions and/or meta.docs sections of rules so that different configs can have different default options?

Impacted Configurations

  • strict
  • strict-type-checked

Additional Info

The example from the thread is https://typescript-eslint.io/rules/restrict-plus-operands/#options.

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.package: eslint-pluginIssues related to @typescript-eslint/eslint-pluginpreset config changeProposal for an addition, removal, or general change to a preset config

    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