Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow per-extension configuration in cascade #2473

Closed
kpdecker opened this issue May 9, 2015 · 1 comment
Closed

Allow per-extension configuration in cascade #2473

kpdecker opened this issue May 9, 2015 · 1 comment
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion

Comments

@kpdecker
Copy link

kpdecker commented May 9, 2015

It would be nice to have a config cascade stage that allows for the config to be altered based on file extension and/or glob pattern. The primary use case for this is to allow for linting of jsx and es6 features while still allowing for linting of grunt/gulp/etc files that are required to bootstrap the jsx/es6 source code.

Strawman:

  "extensions": {
    "es6.js": {
      "rules": {
        "no-var": 1
      }
    },
    "jsx": {
      "ecmaFeatures": {
        "jsx": true
      },
      "plugins": [
        "react"
      ]
    }
  },
@nzakas
Copy link
Member

nzakas commented May 9, 2015

There's a bunch of complexities to this, which is why it's not being committed to yet. However, it is part of our discussions for 2.0.0 (#2203), so follow there for updates.

@nzakas nzakas closed this as completed May 9, 2015
@CrabDude CrabDude mentioned this issue Aug 23, 2016
11 tasks
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 7, 2018
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Feb 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion
Projects
None yet
Development

No branches or pull requests

2 participants