Skip to main content
Jump to: navigation, search


< Orion
Revision as of 13:01, 6 January 2015 by Michael (Talk | contribs) (Rules)

Orion 5.0 moved to ESLint as the validator that ships with Orion. This page captures ongoing issues.


The following table describes all of the rules currently available in Orion and ones that we plan to add in the future.

Rules that are currently available are struck out.

Rule Default Severity Available Since Problem Message Details
block-scoped-var Error - '{variable}' is already defined.
  • Occurs when a function-scoped variable is treated as if it was block scoped.
  • ESLint calls this error '{variable} used outside of binding context.'
brace-style Ignore -    
camelcase Ignore -    
complexity Ignore -    
consistent-this Ignore -    
curly Ignore 6.0 Statements should be enclosed in braces.  
dot-notation Warning - {a} is better written in dot notation.  
eqeqeq Warning 5.0
  • Expected '===' and saw '=='.
  • Expected '!==' and saw '!='.
guard-for-in Ignore - The body of a for in should be wrapped in an if statement to filter unwanted properties from the prototype.  
max-depth Ignore -   Enforces max depth of nested blocks within a function.
max-len Ignore - Line is too long. Enforces a maximum line length.
max-params Ignore -    
max-statements Ignore -    
missing-doc Ignore 5.0 "Missing documentation for function '{name}.'" Flags missing documentation nodes on function declarations and function expressions when they appear as object properties
missing-doc-items Ignore -   Flags missing documentation for parameters, returns, throws, etc on function declarations and function expressions when they appear as object properties
missing-nls Ignore -   Flags String literals that are not properly NLS'd
new-cap Warning - A constructor name should start with an uppercase letter.  
new-parens Error 6.0 Missing parentheses invoking constructor. Flags new Whatever
no-alert Ignore - '{alert, confirm, prompt}' is not defined.  
no-bitwise Warning - Unexpected use of '{operator}'. JSLint disallows bitwise ops by default.
no-caller Error - arguments.{callee, caller} is deprecated. Flags references to arguments.callee and arguments.caller.
no-catch-shadow Warning - '{a}' is already defined.
no-comma-dangle Ignore 8.0 Trailing commas in object expressions are discouraged. Flags trailing commas in object expressions.
no-cond-assign Error 8.0 Expected a conditional expression and instead saw an assignment. Flags assignment in an if/while/do..while/for condition.
no-console Error 8.0 Discouraged use of console in browser-based code. Flags the use of console in browser-based code
no-constant-condition Error 8.0 Discouraged use of constant as a conditional expression. Flags the use of a constant as a conditional expression
no-control-regex Ignore -   Flags control characters (U+0000–U+001F and U+007F) within the source argument to the RegExp constructor.
no-debugger Warning 6.0 debugger' statement use is discouraged.  
no-delete-var Warning - Deleting a local variable is discouraged. Flags an attempt to delete a local variable.
no-div-regex Warning - A regular expression literal can be confused with '/='. Flags a regex literal starting with /=
no-dupe-keys Error 6.0 Duplicate object key '{key}'. Flags object literals that contain the same key more than once.
no-else-return Warning -   Flags an else appearing after an if that contains a return.
no-empty-class Warning - Empty class. Flags an empty character class [] within a regular expression.
no-empty-label Warning - Label '{a}' is not allowed on this statement. Flags a labeled statement that is not a switch, for, or while.
no-empty Warning -   Flags an empty block like if (something) { }.
no-eq-null Error - Use '===' to compare with 'null'.  
no-eval Ignore 6.0 'eval' function calls are discouraged.  
no-ex-assign Warning - Do not assign to the exception parameter.  
no-extra-semi Warning 5.0 Unnecessary semicolon.  
no-extra-strict Warning -   Flags "use strict" on a function when the entire Program is already in strict mode.
no-fallthrough Error - Switch case may be entered by falling through previous case. If intended, add a new comment //$FALL-THROUGH$ on the line above Flags a fallthrough case within a switch statement, unless it is explicitly commented.
no-floating-decimal Warning - A {leading, trailing} decimal point can be confused with a dot: '{n}'. Flags numeric literals that have a leading or trailing decimal point.
no-func-assign Warning -   Flags assignment to a variable that's already bound to a FunctionExpression.
no-global-strict Warning -   Flags "use strict" applied to the entire Program.
no-implied-eval Ignore 6.0 Implicit 'eval' function calls are discouraged. Flags calls to the string-argument form of setTimeout and setInterval, which implicitly perform eval. This rule logic was merged to be part of the no-eval rule.
no-iterator Error 8.0 Discouraged __iterator__ property use. Flags use of __iterator__ as an identifier name or property key.
no-label-var Error - '{label}' is already defined. Flags labels that collide with an identifier.
no-loop-func Error - Don't make functions within a loop.  
no-mixed-requires Ignore -   Flags Node.js require()s that mix different types of requires (core, module, file, computed).
no-mixed-returns Error -   Flags functions that return more than one kind of item, for example returning String and Object
no-multi-str Warning -   Flags use of ES5 multiline string literals.
no-native-reassign Warning -
  • Read only.
  • Bad assignment. (if assigning to undefined)
Flags an attempt to reassign a native object like Math, Array, undefined, etc.
no-negated-in-lhs Warning -  
  • Flags a unary ! operator applied to the LHS of an in statement, which negates the LHS, not the in.
  • Eg. (!"key" in {key: 1}) (which always evaluates to false), will be flagged.
no-new-array Warning - Use the array literal notation []. Flags new Array().
no-new-func Warning - The Function constructor is eval. Flags new Function().
no-new-object Warning - Use the object literal notation {}. Flags new Object().
no-new-wrappers Warning - Do not use {String, Number, Boolean, Math, JSON} as a constructor. Flags new applied to any of those.
no-new Error - Do not use 'new' for side effects. Flags uses of new operator in an expression that is not assigned to anything.
no-obj-calls Warning - Math is not a function..
  • Flags attempts to call object properties of the global object (Math, JSON) as a function, like Math().
no-octal-escape Warning - Bad escapement. Flags octal escapes in strings, for example var x = "Copyright \251";
no-octal Warning - Don't use extra leading zeros '{n}'. Flags number literals that begin with leading 0s, which indicate a (probably accidental) octal literal.
no-plusplus Warning -
  • Unexpected use of '++'
  • Unexpected use of '--'
no-proto Error -
  • Reserved name '__proto__' should not be assigned."
  • 'Reserved name '__proto__' should not be used as a key."
no-redeclare Warning 5.0 '{a}' is already defined. Usually results from having two for loops in the same function that share a loop variable declaration like var i=....
no-regex-spaces Error 8.0 Avoid using multiple spaces in regular expressions. Use ' {${0}}' instead. Flags regular expressions that have two or more subsequent spaces.
no-reserved-keys Error 8.0 Reserved words should not be used as property keys. Checks to see if a JavaScript reserved word is being used as a property key
no-return-assign Warning -  
  • Prevents assignment in a return statement.
  • Unsupported by JSLint, although JSLint does require parens around a return-assignment, eg: return (x = 2);
no-script-url Warning -  
  • Flags string literals beginning with javascript:. (Script URLs are a form of eval.)
no-self-compare Error -   Flags comparisons where the left- and right-hand sides are the same.
no-shadow Warning 8.0 '{a}' is already declared in the upper scope. Flags variables that have the same name as a variable declared in an upper scope.
no-spaced-func Ignore - Unnecessary space in function call. Report on excess space in a function call, for example myFunc (); or new MyObj ();
no-sparse-arrays Warning 8.0 Sparse array declarations should de avoided. Flags sparse arrays with null elements
no-sync Ignore - Unexpected sync method: '{a}'.
  • Flags Node.js's synchronous I/O methods.
  • The stupid option is supported only in newer versions of JSLint (not Orion's).
no-ternary Ignore -   Flags any use of the ternary operator cond ? thenExpr : elseExpr
no-undef-init Warning - It is not necessary to initialize '{variable}' to 'undefined'.  
no-unused-params Warning - "Parameter '{param}' is not used." Flags parameters in function declarations / expressions if they are not being used
no-undef Error 5.0 '{variable}' is not defined.
  • Flags references to a global variable that is not listed in a /*global*/ or /*globals*/ block.
  • Predefined environments (eg. node, browser) can be set in the /*jslint */ block.
no-underscore-dangle Ignore - Dangling '_'  
no-unreachable Error - Unreachable code. Flags statements that occur after a return, throw, etc.
no-unused-expressions Warning - Expected an assignment or function call and instead saw an expression. Flags expressions that appear in a statement context and don't cause side effects.
no-unused-vars Warning 5.0 Function declares unused variable '{a}'.  
no-use-before-define Warning 5.0 '{a}' was used before it was defined.  
no-with Warning - Expected an identifier and instead saw 'with'. Treated as fatal parse error in JSLint.
no-wrap-func Ignore - Do not wrap function literals in parens unless they are to be immediately invoked. Flags a parenthesized function literal that is not immediately invoked, eg. (function fun(){})
object-prototype-external Warning -   Flags calls to methods of Object.prototype that rely on the prototype chain. For example this code should be flagged:
  1. foo.hasOwnProperty("bar")

Example (1) is unsafe, as foo may have a property named hasOwnProperty, or have been constructed via Object.create(null).

As for this:

  1., "bar")

Example (2) technically relies on the prototype chain as well: the hasOwnProperty method is defined on Object.prototype, not Object. Object inherits the methods of Object.prototype through its prototype chain. However (2) is unlikely to fail, as sane JavaScript programs will not modify the global objects' prototypes. If we choose to flag (2), it should only be for style.

one-var Warning - Too many var statements. Allows only 1 var statement per function.
quote-props Warning -   Requires object literal keys to be quoted with " or '.
quotes Ignore -   Flags any use of single or double quote marks, depending on setting.
radix Warning - Missing radix parameter. Warns when parseInt() called without the 2nd parameter (radix).
regex-spaces Warning - Spaces are hard to count. Use {n}.  
semi Warning 5.0 Missing semicolon.  
strict Ignore -   Flags any code that lacks the "use strict" pragma.
throw-error Warning 7.0   Flags code that throws a non-Error, eg. throw "a problem occurred";
use-isnan Error 6.0 Use the isNaN function to compare with NaN.  
wrap-iife Ignore -
  • Wrap the entire immediate function invocation in parens.
  • Move the invocation into the parens that contain the function.
Flags missing parens on immediately-invoked functions, eg. function(){ console.log('hi'); }();
wrap-regex Warning - Wrap the /regexp/ literal in parens to disambiguate the slash operator.  

Implementing a new rule

This section explains how to implement a new linting rule. For brevity, all paths are given relative to bundles/org.eclipse.orion.client.javascript/web/ in the client repo.

First, create the tests and rule:

  1. Create a new test file for the rule at: /eslint/tests/lib/rules/{rule-name}.js.
  2. Link your test to the suite in /eslint/tests/load-tests.js.
  3. Implement the actual logic for your rule in /eslint/lib/load-rules-async.js.

At this point you should run the JS bundle tests and ensure your rule works as intended. To get your rule running in the Orion product's validator, there are additional steps:

  1. Create strings for the validation message(s) generated by your rule in /javascript/nls/root/problems.js.
  2. Create a short string describing what your rule does in /javascript/nls/root/messages.js.
  3. Add an entry to the orion.core.setting declaration in /javascript/plugins/javascriptPlugin.js. This allows your rule to be configured from the JS validator settings page. Make sure it references the same nameKey used in messages.js.
  4. Add a config entry for your rule to the default ESLint config object in /javascript/validator.js.
  5. Add your rule to the #updated() handler in /javascript/validator.js.

Reload the JS plugin, and your rule should now be configurable from the Settings page, and properly set up for translation too.


  • Every rule needs extensive unit tests.
  • Unit tests should use Mocha.

Running the tests

  • To run the ESLint tests as part of the main JavaScript tests suite load {orion-server-url}/javascript/js-tests/JsMochaSuite.html in your web browser.
  • To run just the ESLint rule tests, load {orion-server-url}/js-tests/javascript/JsMochaSuite.html?grep=ESLint%20Rule%20Tests in your browser.
  • To run just the ESLint core tests, load {orion-server-url}/js-tests/javascript/JsMochaSuite.html?grep=ESLint%20Core%20Tests in your browser.
  • To run only a subset of the tests, add ?grep=ESLint%20Rule%20Tests onto the test page URL.

See Mocha usage options for more options.

User interface

  • Should we have a UI for configuring what rules are active? bug 424268.
  • Should we try to support .eslintrc? This would be an ideal project-scope setting.
  • Should we try to honor equivalent JSLint/JSHint flags when possible? For example /*jslint eqeqeq:false */ could disable the eqeqeq rule on a per-file basis.
    • ESLint now has its own syntax for this: /*eslint ..*/, which we are using instead.


We need to support i18n. Pre-req is bug 422278 (orion.edit.validator support for i18n).

Back to the top