Getting eslint-config-eslint in line with coding standards

Per discussion in chat, the goal of this issue is to document (and eventually implement) changes to the Coding Standards and/or eslint-config-eslint to bring both in line as much as possible.

---

Actionable items:

• Enable space-in-parens to enforce no spaces in parentheses
• Enable quote-props (as-needed) to enforce unquoted properties
• Enable lines-around-comment to require blank lines before line and block
• Enable vars-on-top to ensure variables are declared at the top of their containing scope (Note: Might be removed)
• Enable one-var, per @ilyavolodin’s suggestion (Note: Might be removed) Using one-var-declaration-per-line
• Enable one-var-declaration-per-line to enforce declaring one variable per line
• Enable strict to enforce strict mode at the desired scope
• Enable newline-after-var to enforce blank line between variable declarations and first statement
• Enable no-console
• Enable valid-jsdoc if not enabled, use preferType to ensure lowercase builtin types per guidelines.

[mysticatea]

Just my feeling, I hate vars-on-top style…

By the way, Node v6 will be released soon, and we have a plan to drop supports of Node 0.x. After that, I guess we use no-var rule. The let declarations are block-scoped, so I think we will get worse upgrade path if we apply vars-on-top now.

[platinumazure]

Fine by me. Closing. Thanks everyone for your help!