Hi Nicholas,

quick update: I deinstalled and installed `eslint` again (with and without 
`-g`). Now I get this, but with no error (because of missing @return):

xxxx:xxxx user$ eslint app/onboarding.js --config .eslintrc
xxxx:xxxx user$

The file still looks like on the Gist.

Am Dienstag, 2. Mai 2017 17:45:19 UTC+2 schrieb Stefan:
>
> Hi Nicholas,
>
> Thanks for your response. I updated the Gist 
> <https://gist.github.com/natterstefan/3121af83f5f98ee05311d85766ed0d67> and 
> included all the necessary details you asked for. When I run the command in 
> the command line I got this:
>
> ixxxx:xxxx xxxx$ eslint app/onboarding.js --config .eslintrc
>
> /Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint-config-airbnb/node_modules/eslint-config-airbnb-base/rules/es6.js:
> Configuration for rule "arrow-parens" is invalid:
> Value "as-needed,[object Object]" has more items than allowed.
>
> Referenced from: 
> /Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint-config-airbnb/node_modules/eslint-config-airbnb-base/index.js
> Referenced from: airbnb
> Referenced from: /Users/xxxx/sandbox/xxxx/.eslintrc
> Error: 
> /Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint-config-airbnb/node_modules/eslint-config-airbnb-base/rules/es6.js:
> Configuration for rule "arrow-parens" is invalid:
> Value "as-needed,[object Object]" has more items than allowed.
>
> Referenced from: 
> /Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint-config-airbnb/node_modules/eslint-config-airbnb-base/index.js
> Referenced from: airbnb
> Referenced from: /Users/xxxx/sandbox/xxxx/.eslintrc
>     at validateRuleOptions 
> (/Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint/lib/config/config-validator.js:116:15)
>     at 
> /Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint/lib/config/config-validator.js:163:13
>     at Array.forEach (native)
>     at Object.validate 
> (/Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint/lib/config/config-validator.js:162:35)
>     at load 
> (/Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint/lib/config/config-file.js:523:19)
>     at 
> /Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint/lib/config/config-file.js:392:36
>     at Array.reduceRight (native)
>     at applyExtends 
> (/Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint/lib/config/config-file.js:363:28)
>     at load 
> (/Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint/lib/config/config-file.js:530:22)
>     at 
> /Users/xxxx/.nvm/versions/node/v4.2.6/lib/node_modules/eslint/lib/config/config-file.js:392:36
>
> Does this help you?
>
>
> Am Dienstag, 2. Mai 2017 17:08:09 UTC+2 schrieb Nicholas Zakas:
>>
>> Can you try using ESLint on the command line with that file? If that 
>> gives you the output you expect, then it's likely Atom is not configured 
>> properly. If that doesn't give you what you expect, can you share the JSDoc 
>> comment you're linting and show your configuration for those two rules?
>> On Mon, May 1, 2017 at 11:11 PM Stefan Natter <[email protected]> 
>> wrote:
>>
>>> Hey guys,
>>>
>>> I do not get the rules `require-jsdoc` and `valid-jsdoc` running in my 
>>> .eslintrc.json (see Gist 
>>> <https://gist.github.com/natterstefan/3121af83f5f98ee05311d85766ed0d67>). 
>>> In my test.js-file I have a missing `return` and `ParamDescription` in the 
>>> comments. But my ESLint does not mark the file as invalid. I am using Atom 
>>> and the latest version of the `eslint` plugin. 
>>>
>>> Can someone help me please?
>>>
>>> PS: do I need to install https://github.com/gajus/eslint-plugin-jsdoc or 
>>> another plugin?
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "ESLint" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"ESLint" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to