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

Incorrect "invalid configuration" message for warning rule #5653

Closed
s0ph1e opened this issue Mar 23, 2016 · 1 comment
Closed

Incorrect "invalid configuration" message for warning rule #5653

s0ph1e opened this issue Mar 23, 2016 · 1 comment
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion bug ESLint is working incorrectly core Relates to ESLint's core APIs and features

Comments

@s0ph1e
Copy link
Contributor

s0ph1e commented Mar 23, 2016

What version of ESLint are you using? v2.4.0

Please show your full configuration:

rules:
  curly: "warning"

What did you do? Please include the actual source code causing the issue.
Run eslint app.js

What did you expect to happen?
According to documentaion error message should say
Severity should be one of the following: 0 = off, 1 = warn, 2 = error (you passed '"warning"')
instead of
Severity should be one of the following: 0 = off, 1 = warning, 2 = error (you passed '"warning"')

What actually happened? Please include the actual, raw output from ESLint.

Error: /home/administrator/Projects/my/test/.eslintrc.yml:
    Configuration for rule "curly" is invalid:
    Severity should be one of the following: 0 = off, 1 = warning, 2 = error (you passed '"warning"').

    at validateRuleOptions (/usr/lib/node_modules/eslint/lib/config/config-validator.js:118:15)
    at /usr/lib/node_modules/eslint/lib/config/config-validator.js:164:13
    at Array.forEach (native)
    at Object.validate (/usr/lib/node_modules/eslint/lib/config/config-validator.js:163:35)
    at Object.load (/usr/lib/node_modules/eslint/lib/config/config-file.js:457:19)
    at loadConfig (/usr/lib/node_modules/eslint/lib/config.js:67:33)
    at getLocalConfig (/usr/lib/node_modules/eslint/lib/config.js:129:23)
    at Config.getConfig (/usr/lib/node_modules/eslint/lib/config.js:223:22)
    at processText (/usr/lib/node_modules/eslint/lib/cli-engine.js:155:27)
    at processFile (/usr/lib/node_modules/eslint/lib/cli-engine.js:227:18)

@eslintbot eslintbot added the triage An ESLint team member will look at this issue soon label Mar 23, 2016
@platinumazure platinumazure added bug ESLint is working incorrectly core Relates to ESLint's core APIs and features accepted There is consensus among the team that this change meets the criteria for inclusion and removed triage An ESLint team member will look at this issue soon labels Mar 23, 2016
@platinumazure
Copy link
Member

Confirmed here.

ilyavolodin added a commit that referenced this issue Mar 23, 2016
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 6, 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 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion bug ESLint is working incorrectly core Relates to ESLint's core APIs and features
Projects
None yet
Development

No branches or pull requests

3 participants