-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
tools: enable space-after-keywords eslint rule #2430
Conversation
I like it. LGTM |
LGTM |
Not a big fan of new-cap. |
Would you prefer the tests be refractored so no arguments are called with |
No, I just don't think newIsCap is a very good rule. I'd leave it out. |
eg changes: if(x) { ... } to: if (x) { ... }
Requires that you do: if (x) { ... } Rather than: if(x) { ... }
ccca992
to
2e2f255
Compare
PTAL @bnoordhuis, i've removed the rule. |
LGTM |
@brendanashworth did you include the commit metadata on those? |
Oh no, looks like I missed that.. a little bit late but thank you for On Saturday, August 22, 2015, Colin Ihrig notifications@github.com wrote:
|
This adds a new eslint rule:
space-after-keywords
.Spaces after keywords makes this error (6 now fixed errors):
in favor of: