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

Use different standard configs for different subfolders #896

Closed
lohfu opened this issue May 28, 2017 · 4 comments

Comments

@lohfu
Copy link

commented May 28, 2017

Hi,

I am using the regular standard tool to lint both my front end code and back end code. However, I don't understand how to use more configs than the standard?

For example I have 3 different folders requiring different configs:

  • /client/admin - uses [ "standard, "standard-react" ]
  • /client/public - uses [ "standard, "standard-preact" ]
  • /server - uses [ "standard" ]

Currently i have just gone with using the regular eslint CLI and setting up different .eslintrc files in the respective folders... but i would like to solve this with just the standard CLI and configuration if possible.

@ifraixedes

This comment has been minimized.

Copy link

commented May 29, 2017

What's the problem having an .eslintrc file inside of each folder?

@batiste

This comment has been minimized.

Copy link

commented May 29, 2017

I have a somewhat similar request. I do have an .eslintrc in a subfolder (compat plugin form browser JS) but standard seems to ignore it. Is there anyway to make standard use this file under this directory?

@Flet

This comment has been minimized.

Copy link
Member

commented May 30, 2017

The only way to accomplish this would be separate .eslintrc files (and using eslint-config-standard with eslint directly instead of using the standard CLI).

@lohfu

This comment has been minimized.

Copy link
Author

commented May 30, 2017

@ifraixedes no real problems, i was just curious to see if there was a way to do using the standard CLI

@Flet yup that's what i'm doing. i will just continue doing that and close this issue.

@lohfu lohfu closed this May 30, 2017

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
4 participants
You can’t perform that action at this time.