Switch to ESLint about baumeister HOT 5 CLOSED

I don't know sindres config in particular, but the move to eslint is essential. It has better guideline detection in addition to the linting, which I also find better. Plus the es6 linting which we are currently not using though. I have created my eslint file, and therfore coding guideline, over the last month which I really like. Sometimes I feel pissed when another config stops me from being lean and creative just for the guideline's sake.

For example my beloved one liner shortcut: if (falsy) return; which, in most config is not allowed.

But I guess this needs some discussion and I am totally willing to take one external maintained config, as long as we are concise in the particular project.

from baumeister.

Sorry for the bad English :D I am being actively autocorrected by my mobile.

from baumeister.

hehe 😄

Thanks for the feedback.

My personal gist of it: You agree with using XOXO.

Cause the following isn’t a problem with XOXO:

Sometimes I feel pissed when another config stops me from being lean and creative just for the guideline's sake.

We are able to Override any of the default rules. See Readme of XOXO: https://github.com/sindresorhus/xo#rules

Here you can see the defaults:
https://github.com/sindresorhus/eslint-config-xo/blob/master/index.js

from baumeister.

@krnlde I just replaced JSHint with ESLint in the develop branch 💖

But I decided against using XO as a wrapper for ESLint and only pulled in the shared config from XO directly. See package.json

In our .eslintrc you can see how easy it is to override rules from eslint-config-xo

from baumeister.

Done in develop branch. Will make it into master in the next release.

from baumeister.