Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd optional capability to add more restrictive rules. #349
Comments
ericwooley
changed the title
Add optional capability to restrict more rules.
Add optional capability to add more restrictive rules.
Dec 1, 2015
This comment has been minimized.
This comment has been minimized.
pbrinkmeier
commented
Dec 1, 2015
|
|
This comment has been minimized.
This comment has been minimized.
|
What about using eslint directly, while extending the standard rule set? https://github.com/feross/eslint-config-standard Would that work? |
This comment has been minimized.
This comment has been minimized.
|
@bcomnes has proposed the [already] suggested solution for dealing with this. |
dcousens
closed this
Dec 2, 2015
dcousens
added
the
question
label
Dec 2, 2015
This comment has been minimized.
This comment has been minimized.
|
Yep, as @bcomnes suggests, just add this to your {
"extends": "standard"
} |
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.
ericwooley commentedDec 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.