-
Notifications
You must be signed in to change notification settings - Fork 57
[RFR] Switch to ESlint #388
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
Conversation
Awesome work! Feels really good to remove all these ignore comments. |
Plus it's driving out much more possible issues than JShint. @valeriangalliat feel free to hack in if you see something. |
Terrific. Only the tests to fix before merging. :) |
Something to discuss:
http://eslint.org/docs/rules/no-process-exit.html I guess we can mute this rule. |
Any reason we do exit instead of throwing an error? |
To control the exit code. +1 to mute the rule, it's not meaningful in the CLI, it's only relevant inside the library code (and we don't exit from the library). |
|
Yeah, I removed my comment, just realized the |
So this is now Ready for review :-) We are using all of ESlint default rules, overriding just the few ones we "don't agree" with. Another option is not to use any base rules with If you see something that should be added ? |
I like it as is, okay to merge. 👍 |
What about moving to adding a space between function declaration name and params. function whatever (foo, bar) { ... } |
I'm all for following standard. I'm also okay with semistandard which is basically like standard but with semicolons (and thus will be more friendly with our codebase). |
space-before-function-parentheses
orspace-before-function-paren
does not seem to work