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

Add optional capability to add more restrictive rules. #349

Closed
ericwooley opened this issue Dec 1, 2015 · 4 comments

Comments

@ericwooley
Copy link

commented Dec 1, 2015

I'm on board with standard, but there are some rules that I want that standard doesn't enforce. I propose a merge of standard with eslint options, where standard overwrites eslintrc rules, but allows additional rules to be enforced. For example I would like to use no-long-files but don't think it should be included as a standard, because it's too difficult to determine an appropriate size, yet it's very difficult to enforce this rule without two linters fighting eachother.

Standard is great, but it's too hard to use in combination with eslint. Life would be considerably easier if standard respected additional eslint rules that don't conflict with the standard rules. This wouldn't conflict with standards goal, because a more restricted ruleset still satisfies the standard requirements.

@ericwooley ericwooley changed the title Add optional capability to restrict more rules. Add optional capability to add more restrictive rules. Dec 1, 2015

@pbrinkmeier

This comment has been minimized.

Copy link

commented Dec 1, 2015

👍

@bcomnes

This comment has been minimized.

Copy link
Member

commented Dec 2, 2015

What about using eslint directly, while extending the standard rule set? https://github.com/feross/eslint-config-standard Would that work?

@dcousens

This comment has been minimized.

Copy link
Member

commented Dec 2, 2015

@bcomnes has proposed the [already] suggested solution for dealing with this.

👍 , closing.

@dcousens dcousens closed this Dec 2, 2015

@dcousens dcousens added the question label Dec 2, 2015

@feross

This comment has been minimized.

Copy link
Member

commented Dec 2, 2015

Yep, as @bcomnes suggests, just add this to your .eslintrc and customize away!

{
  "extends": "standard"
}

@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.
5 participants
You can’t perform that action at this time.