-
Notifications
You must be signed in to change notification settings - Fork 110
Conversation
Thanks @toxamiz! I'll review the linting rules over the next few days, looks like a really good start though. We should also be looking at tools like https://www.npmjs.com/package/husky for when commits are made and ideally everything is formatted automatically. I'm a bit skeptical on whether eslint supports some of the rules that we use, if it does that's great but we'll still need a way to automatically format them |
For first look there are some indent issues (or the base file have indent issues :) ) and there no base rule for UpperCamesCase for global functions |
Looks good @toxamiz, some more feedback:
We need to make a conscious effort that the Looking at a plugin like: https://www.npmjs.com/package/eslint-plugin-ie11 might be a suitable option, or at least inheriting some of the rules from this. |
'browser': true | ||
}, | ||
'parserOptions': { | ||
'ecmaVersion': 5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'ecmaVersion': 5 | |
'ecmaVersion': 5 |
I'm not confident this supports IE8-11 rules
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It just forbid to use es6 syntax e.g. let
, const
, etc
I don't think it is what we need I tried to use https://github.com/amilajack/eslint-plugin-compat which should lint the browser compatibility, but i doesn't work properly: allowing to use [].map on ie8 for example. Btw, don't you think about to just require With es5 requirement we can use |
I've tried to configure eslint rules, based on
scripts/helper.js
. Can use this for more accurate further settings.