Sort out all of the undecided rules!

Author: robertrossmann

coding-styles/base.js

@@ -138,6 +138,12 @@ module.exports = {
       ]
     }],
 
+    // Validate Indentation
+    // This rule is aimed to enforce consistent indentation style.
+    'indent': [1, 2, {
+      SwitchCase: 1
+    }],
+
     // Enforce Property Spacing
     // This rule will warn when spacing in properties does not match the specified options. In the case
     // of long lines, it is acceptable to add a new line wherever whitespace is allowed.
@@ -147,6 +153,12 @@ module.exports = {
       mode: 'strict'
     }],
 
+    // This rule will enforce consistency of spacing around keywords and keyword-like tokens
+    'keyword-spacing': [1, {
+      before: true,
+      after: true
+    }],
+
     // Disallow mixing CRLF and LF linebreaks
     // This rule aims to ensure having consistent line endings independent of operating system.
     'linebreak-style': [2, 'unix'],
@@ -290,14 +302,19 @@ module.exports = {
     // This rule is aimed at ensuring there are spaces around infix operators.
     'space-infix-ops': 1,
 
-    // This rule will enforce consistency of spacing around keywords and keyword-like tokens
-    'keyword-spacing': [1, {
-      before: true,
-      after: true
+    // Require or disallow spaces before/after unary operators
+    // This rule enforces consistency regarding the spaces after words unary operators and after/before
+    // nonwords unary operators.
+    'space-unary-ops': [1, {
+      words: true,
+      nonwords: false
     }],
 
     // Require or disallow a whitespace beginning a comment
     // This rule will enforce consistency of spacing after the start of a comment // or /*.
-    'spaced-comment': 1
+    'spaced-comment': 1,
+
+    // Require IIFEs to be Wrapped
+    'wrap-iife': [1, 'inside']
   }
 }

environments/nodejs/best-practices.js

@@ -51,6 +51,10 @@ module.exports = {
     // modified after the initial assignment. This helps v8 to better optimise code at runtime.
     'prefer-const': 1,
 
+    // Suggest using Reflect methods where applicable
+    // Reflection API is still unsupported in Node.js (as of v5.5)
+    'prefer-reflect': 0,
+
     // Suggest using the spread operator instead of .apply()
     // This rule is aimed to flag usage of Function.prototype.apply() that can be replaced with the
     // spread operator.

standard/best-practices.js

@@ -14,6 +14,13 @@ module.exports = {
     // Never allow trailing commas
     'comma-dangle': [2, 'never'],
 
+    // Require Function Expressions to have a Name
+    // If you provide the optional name for a function expression then you will get the name of the
+    // function expression in the stack trace.
+    // If you are tempted to create anonymous function expression, consider using arrow function
+    // instead.
+    'func-names': 1,
+
     // Disallow lexical declarations in case/default clauses
     // This rule disallows lexical declarations (let, const, function and class) in case/default
     // clauses. The reason is that the lexical declaration is visible in the entire switch block but it
@@ -171,6 +178,9 @@ module.exports = {
     // Additionally, the with statement cannot be used in strict mode.
     'no-with': 2,
 
+    // Suggest using Reflect methods where applicable
+    'prefer-reflect': 1,
+
     // Require Variable Declarations to be at the top of their scope
     // This rule aims to keep all variable declarations in the leading series of statements. Allowing
     // multiple declarations helps promote maintainability.

standard/known-errors.js

@@ -260,6 +260,9 @@ module.exports = {
     'no-unused-expressions': [2, {
       allowShortCircuit: true,
       allowTernary: true
-    }]
+    }],
+
+    // Disallow generator functions that do not have yield
+    'require-yield': 2
   }
 }

standard/optional.js

@@ -35,12 +35,22 @@ module.exports = {
       location: 'anywhere'
     }],
 
+    // Limit Maximum Depth
+    // This rule aims to reduce the complexity of your code by allowing you to configure the maximum
+    // depth blocks can be nested in a function.
+    'max-depth': [1, 4],
+
     // Limit Maximum Length of Line
     // Very long lines of code in any language can be difficult to read. In order to aid in readability
     // and maintainability many coders have developed a convention to limit lines of code to a certain
     // number of characters.
     'max-len': [1, 100, 2],
 
+    // Limit Maximum Number of Parameters
+    // Functions that take numerous parameters can be difficult to read and write because it requires
+    // the memorization of what each parameter is, its type, and the order they should appear in.
+    'max-params': [1, 3],
+
     // Disallow Bitwise Operators
     // This rule is aimed at catching typos that end up as bitwise operators, but are meant to be the
     // much more common &&, ||, <, > operators.

undecided.js

@@ -71,6 +71,11 @@ module.exports = {
     // Unused, these operators are quite useful as long as whitespace is used responsibly around them.
     'no-plusplus': 0,
 
+    // Disallow use of the void operator
+    // void is quite useful with IIFEs and for discarding return values when using return for
+    // short-circuiting.
+    'no-void': 0,
+
     // Require IDs to match a pattern
     // Unused, too restrictive.
     'id-match': 0,
@@ -92,10 +97,6 @@ module.exports = {
     // Unused, too restrictive.
     'no-negated-condition': 0,
 
-    // Disallow certain syntax
-    // Unused, no use case.
-    'no-restricted-syntax': 0,
-
     // Disallow Ternary Operators
     // You kidding me? Ternaries are great!
     'no-ternary': 0,
@@ -108,6 +109,17 @@ module.exports = {
     // Unused, too restrictive. It was flagging i.e. `array.indexOf('a') !== -1` (is 'a' in this array?)
     // as errors. Also, status code checks in HTTP responses were being reported as issues.
     // While I generally like the idea, current implementation simply won't fly well.
-    'no-magic-numbers': 0
+    'no-magic-numbers': 0,
+
+    // Require Radix Parameter
+    // This rule is aimed at preventing the unintended conversion of a string to a number of a
+    // different base than intended.
+    // Unused, too restrictive. Front-end team might have some interest in this as the whole radix
+    // issue started with different browsers using different radix for different numbers.
+    'radix': 0,
+
+    // Require Regex Literals to be Wrapped
+    // Unused, too restrictive.
+    'wrap-regex': 0
   }
 }