-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
'use strict' in all of the files #342
Comments
CC: @feross (since there's an obvious connection there) |
I've never personally had the need to use I personally don't think it's worth the overhead of maintaining a custom |
I was thinking of using the custom |
@malept Why do you need to install |
Editor integration is easier that way. |
Ahh, you can also just add {
"extends": "standard"
} |
|
For me, most of these errors are ridiculous. |
I have no problem with this one.
This one is reasonable. We should avoid shadowed variables.
For some reason, I couldn't get this one to show up when I was messing with it last night. The rest we should disable. |
This warning about function parameters. Not about local variables. Currently, we have callback hell. In my fork I use Promises. But anyway it is incorrect — it is ok and legal to shadow top-level function parameter. Real solution — use Promise/await cannot be done in "fix style" commit. Easy fix — just rename param — not acceptable, I think. Modern languages, like Kotlin, allows me to shadow top-level member. BTW, I want to use |
It is the most annoying warning — you have to write "var foo = function() {". It is ridiculous. http://eslint.org/docs/rules/func-style#expression |
(cherry picked from commit 02260d9)
Moving conversation from #341.
I am not against using
'use strict'
, but if we do so, I'd like to consider switching to usingstrict-standard
instead ofstandard
. Or possiblyeslint
+eslint-config-standard
+ some strict config (the reasoning being that it's more likely that a given editor will have eslint support available more readily thanstandard
- this may just mean that we keep some form ofstandard
fornpm test
, and just add an.eslintrc
to the project).See also:
The text was updated successfully, but these errors were encountered: