Added eslint based on airbnb config

[zerkms]

I understand that linting is a personal thing but I think that even with the base airbnb config and modified indentation it catches a lot of style inconsistencies.

And it is definitely better than not to have any linter at all.

What do you think?

[coveralls]

Coverage remained the same at 98.214% when pulling 577941f on zerkms:ESLINT_AIRBNB into c1357b8 on tomkp:master.

[tomkp]

I completely agree - I've had this on my todo list for a while.

[zerkms]

So what do you think about adding this then? Majority of code already complies with it, also catches few inconsistencies here and there and probably couple of rules might be changed.

Here is the config I'm using in all my projects:

{
    "extends": "airbnb",

    "parser": "babel-eslint",

    "rules": {
        "max-len": [2, 120, 4, {
            "ignoreUrls": true,
            "ignoreComments": false
        }],
        "indent": [2, 4],
        "react/jsx-indent-props": [2, 4],
        "space-before-function-paren": [2, "never"]
    }
}

[tomkp]

I'm going to merge this in - I guess we need to ensure the codebase is compliant, and then set it up to run automatically (probably as part of the compile step)...

[tomkp]

Thanks!

[zerkms]

I guess we need to ensure the codebase is compliant

Yep, I will send the PR with changes to the code some time today

and then set it up to run automatically (probably as part of the compile step)

That's also personal: I don't personally do that in any of my projects, since even though I think the style is important, it's okay if some commit does not comply with it. But I'm open for the dialogue :-)

[tomkp]

Great - thanks a lot...
I guess we can make a decision on wether to enforce the linting later... although I think I like the idea of it being mandatory.

[zerkms]

Yep, makes sense

I have fixed style inconsistencies for Pane and Resizer zerkms@132398f

but SplitPane requires some extra effort due to its size so I will do that later.