yoctore/yoctopus-generator

View on GitHub
app/templates/applications/node/app/controllers/_.request.js

Summary

Maintainability
A
2 hrs
Test Coverage

Function has a complexity of 10.
Open

exports.api = function (req, res) {

Limit Cyclomatic Complexity (complexity)

Cyclomatic complexity measures the number of linearly independent paths through a program's source code. This rule allows setting a cyclomatic complexity threshold.

function a(x) {
    if (true) {
        return x; // 1st path
    } else if (false) {
        return x+1; // 2nd path
    } else {
        return 4; // 3rd path
    }
}

Rule Details

This rule is aimed at reducing code complexity by capping the amount of cyclomatic complexity allowed in a program. As such, it will warn when the cyclomatic complexity crosses the configured threshold (default is 20).

Examples of incorrect code for a maximum of 2:

/*eslint complexity: ["error", 2]*/

function a(x) {
    if (true) {
        return x;
    } else if (false) {
        return x+1;
    } else {
        return 4; // 3rd path
    }
}

Examples of correct code for a maximum of 2:

/*eslint complexity: ["error", 2]*/

function a(x) {
    if (true) {
        return x;
    } else {
        return 4;
    }
}

Options

Optionally, you may specify a max object property:

"complexity": ["error", 2]

is equivalent to

"complexity": ["error", { "max": 2 }]

Deprecated: the object property maximum is deprecated. Please use the property max instead.

When Not To Use It

If you can't determine an appropriate complexity limit for your code, then it's best to disable this rule.

Further Reading

Related Rules

  • [max-depth](max-depth.md)
  • [max-len](max-len.md)
  • [max-nested-callbacks](max-nested-callbacks.md)
  • [max-params](max-params.md)
  • [max-statements](max-statements.md) Source: http://eslint.org/docs/rules/

Function api has 31 lines of code (exceeds 25 allowed). Consider refactoring.
Open

exports.api = function (req, res) {
  // Retrieve api information
  var api      = this.get('config').config.api;
  // Retrieve app information
  var app      = this.get('config').config.app;
Severity: Minor
Found in app/templates/applications/node/app/controllers/_.request.js - About 1 hr to fix

    Function api has a Cognitive Complexity of 8 (exceeds 5 allowed). Consider refactoring.
    Open

    exports.api = function (req, res) {
      // Retrieve api information
      var api      = this.get('config').config.api;
      // Retrieve app information
      var app      = this.get('config').config.app;
    Severity: Minor
    Found in app/templates/applications/node/app/controllers/_.request.js - About 45 mins to fix

    Cognitive Complexity

    Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

    A method's cognitive complexity is based on a few simple rules:

    • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
    • Code is considered more complex for each "break in the linear flow of the code"
    • Code is considered more complex when "flow breaking structures are nested"

    Further reading

    Irregular whitespace not allowed.
    Open

          'x-origin-ip'        : _.isEmpty(clientIp) || _.isUndefined(clientIp) ? '' : clientIp,

    disallow irregular whitespace (no-irregular-whitespace)

    Invalid or irregular whitespace causes issues with ECMAScript 5 parsers and also makes code harder to debug in a similar nature to mixed tabs and spaces.

    Various whitespace characters can be inputted by programmers by mistake for example from copying or keyboard shortcuts. Pressing Alt + Space on OS X adds in a non breaking space character for example.

    Known issues these spaces cause:

    • Zero Width Space
      • Is NOT considered a separator for tokens and is often parsed as an Unexpected token ILLEGAL
      • Is NOT shown in modern browsers making code repository software expected to resolve the visualisation
    • Line Separator
      • Is NOT a valid character within JSON which would cause parse errors

    Rule Details

    This rule is aimed at catching invalid whitespace that is not a normal tab and space. Some of these characters may cause issues in modern browsers and others will be a debugging issue to spot.

    This rule disallows the following characters except where the options allow:

    \u000B - Line Tabulation (\v) - <vt>
    \u000C - Form Feed (\f) - <ff>
    \u00A0 - No-Break Space - <nbsp>
    \u0085 - Next Line
    \u1680 - Ogham Space Mark
    \u180E - Mongolian Vowel Separator - <mvs>
    \ufeff - Zero Width No-Break Space - <bom>
    \u2000 - En Quad
    \u2001 - Em Quad
    \u2002 - En Space - <ensp>
    \u2003 - Em Space - <emsp>
    \u2004 - Tree-Per-Em
    \u2005 - Four-Per-Em
    \u2006 - Six-Per-Em
    \u2007 - Figure Space
    \u2008 - Punctuation Space - <puncsp>
    \u2009 - Thin Space
    \u200A - Hair Space
    \u200B - Zero Width Space - <zwsp>
    \u2028 - Line Separator
    \u2029 - Paragraph Separator
    \u202F - Narrow No-Break Space
    \u205f - Medium Mathematical Space
    \u3000 - Ideographic Space</zwsp></puncsp></emsp></ensp></bom></mvs></nbsp></ff></vt>

    Options

    This rule has an object option for exceptions:

    • "skipStrings": true (default) allows any whitespace characters in string literals
    • "skipComments": true allows any whitespace characters in comments
    • "skipRegExps": true allows any whitespace characters in regular expression literals
    • "skipTemplates": true allows any whitespace characters in template literals

    skipStrings

    Examples of incorrect code for this rule with the default { "skipStrings": true } option:

    /*eslint no-irregular-whitespace: "error"*/
    
    function thing() /*<nbsp>*/{
        return 'test';
    }
    
    function thing( /*<nbsp>*/){
        return 'test';
    }
    
    function thing /*<nbsp>*/(){
        return 'test';
    }
    
    function thing᠎/*<mvs>*/(){
        return 'test';
    }
    
    function thing() {
        return 'test'; /*<ensp>*/
    }
    
    function thing() {
        return 'test'; /*<nbsp>*/
    }
    
    function thing() {
        // Description <nbsp>: some descriptive text
    }
    
    /*
    Description <nbsp>: some descriptive text
    */
    
    function thing() {
        return / <nbsp>regexp/;
    }
    
    /*eslint-env es6*/
    function thing() {
        return `template <nbsp>string`;
    }</nbsp></nbsp></nbsp></nbsp></nbsp></ensp></mvs></nbsp></nbsp></nbsp>

    Examples of correct code for this rule with the default { "skipStrings": true } option:

    /*eslint no-irregular-whitespace: "error"*/
    
    function thing() {
        return ' <nbsp>thing';
    }
    
    function thing() {
        return '​<zwsp>thing';
    }
    
    function thing() {
        return 'th <nbsp>ing';
    }</nbsp></zwsp></nbsp>

    skipComments

    Examples of additional correct code for this rule with the { "skipComments": true } option:

    /*eslint no-irregular-whitespace: ["error", { "skipComments": true }]*/
    
    function thing() {
        // Description <nbsp>: some descriptive text
    }
    
    /*
    Description <nbsp>: some descriptive text
    */</nbsp></nbsp>

    skipRegExps

    Examples of additional correct code for this rule with the { "skipRegExps": true } option:

    /*eslint no-irregular-whitespace: ["error", { "skipRegExps": true }]*/
    
    function thing() {
        return / <nbsp>regexp/;
    }</nbsp>

    skipTemplates

    Examples of additional correct code for this rule with the { "skipTemplates": true } option:

    /*eslint no-irregular-whitespace: ["error", { "skipTemplates": true }]*/
    /*eslint-env es6*/
    
    function thing() {
        return `template <nbsp>string`;
    }</nbsp>

    When Not To Use It

    If you decide that you wish to use whitespace other than tabs and spaces outside of strings in your application.

    Further Reading

    Unexpected trailing comma.
    Open

          'x-origin-host'      : _.isUndefined(host) ? '' : host,

    require or disallow trailing commas (comma-dangle)

    Trailing commas in object literals are valid according to the ECMAScript 5 (and ECMAScript 3!) spec. However, IE8 (when not in IE8 document mode) and below will throw an error when it encounters trailing commas in JavaScript.

    var foo = {
        bar: "baz",
        qux: "quux",
    };

    Trailing commas simplify adding and removing items to objects and arrays, since only the lines you are modifying must be touched. Another argument in favor of trailing commas is that it improves the clarity of diffs when an item is added or removed from an object or array:

    Less clear:

    var foo = {
    -    bar: "baz",
    -    qux: "quux"
    +    bar: "baz"
     };

    More clear:

    var foo = {
         bar: "baz",
    -    qux: "quux",
     };

    Rule Details

    This rule enforces consistent use of trailing commas in object and array literals.

    Options

    This rule has a string option or an object option:

    {
        "comma-dangle": ["error", "never"],
        // or
        "comma-dangle": ["error", {
            "arrays": "never",
            "objects": "never",
            "imports": "never",
            "exports": "never",
            "functions": "ignore",
        }]
    }
    • "never" (default) disallows trailing commas
    • "always" requires trailing commas
    • "always-multiline" requires trailing commas when the last element or property is in a different line than the closing ] or } and disallows trailing commas when the last element or property is on the same line as the closing ] or }
    • "only-multiline" allows (but does not require) trailing commas when the last element or property is in a different line than the closing ] or } and disallows trailing commas when the last element or property is on the same line as the closing ] or }

    Trailing commas in function declarations and function calls are valid syntax since ECMAScript 2017; however, the string option does not check these situations for backwards compatibility.

    You can also use an object option to configure this rule for each type of syntax. Each of the following options can be set to "never", "always", "always-multiline", "only-multiline", or "ignore". The default for each option is "never" unless otherwise specified.

    • arrays is for array literals and array patterns of destructuring. (e.g. let [a,] = [1,];)
    • objects is for object literals and object patterns of destructuring. (e.g. let {a,} = {a: 1};)
    • imports is for import declarations of ES Modules. (e.g. import {a,} from "foo";)
    • exports is for export declarations of ES Modules. (e.g. export {a,};)
    • functions is for function declarations and function calls. (e.g. (function(a,){ })(b,);)
      functions is set to "ignore" by default for consistency with the string option.

    never

    Examples of incorrect code for this rule with the default "never" option:

    /*eslint comma-dangle: ["error", "never"]*/
    
    var foo = {
        bar: "baz",
        qux: "quux",
    };
    
    var arr = [1,2,];
    
    foo({
      bar: "baz",
      qux: "quux",
    });

    Examples of correct code for this rule with the default "never" option:

    /*eslint comma-dangle: ["error", "never"]*/
    
    var foo = {
        bar: "baz",
        qux: "quux"
    };
    
    var arr = [1,2];
    
    foo({
      bar: "baz",
      qux: "quux"
    });

    always

    Examples of incorrect code for this rule with the "always" option:

    /*eslint comma-dangle: ["error", "always"]*/
    
    var foo = {
        bar: "baz",
        qux: "quux"
    };
    
    var arr = [1,2];
    
    foo({
      bar: "baz",
      qux: "quux"
    });

    Examples of correct code for this rule with the "always" option:

    /*eslint comma-dangle: ["error", "always"]*/
    
    var foo = {
        bar: "baz",
        qux: "quux",
    };
    
    var arr = [1,2,];
    
    foo({
      bar: "baz",
      qux: "quux",
    });

    always-multiline

    Examples of incorrect code for this rule with the "always-multiline" option:

    /*eslint comma-dangle: ["error", "always-multiline"]*/
    
    var foo = {
        bar: "baz",
        qux: "quux"
    };
    
    var foo = { bar: "baz", qux: "quux", };
    
    var arr = [1,2,];
    
    var arr = [1,
        2,];
    
    var arr = [
        1,
        2
    ];
    
    foo({
      bar: "baz",
      qux: "quux"
    });

    Examples of correct code for this rule with the "always-multiline" option:

    /*eslint comma-dangle: ["error", "always-multiline"]*/
    
    var foo = {
        bar: "baz",
        qux: "quux",
    };
    
    var foo = {bar: "baz", qux: "quux"};
    var arr = [1,2];
    
    var arr = [1,
        2];
    
    var arr = [
        1,
        2,
    ];
    
    foo({
      bar: "baz",
      qux: "quux",
    });

    only-multiline

    Examples of incorrect code for this rule with the "only-multiline" option:

    /*eslint comma-dangle: ["error", "only-multiline"]*/
    
    var foo = { bar: "baz", qux: "quux", };
    
    var arr = [1,2,];
    
    var arr = [1,
        2,];

    Examples of correct code for this rule with the "only-multiline" option:

    /*eslint comma-dangle: ["error", "only-multiline"]*/
    
    var foo = {
        bar: "baz",
        qux: "quux",
    };
    
    var foo = {
        bar: "baz",
        qux: "quux"
    };
    
    var foo = {bar: "baz", qux: "quux"};
    var arr = [1,2];
    
    var arr = [1,
        2];
    
    var arr = [
        1,
        2,
    ];
    
    var arr = [
        1,
        2
    ];
    
    foo({
      bar: "baz",
      qux: "quux",
    });
    
    foo({
      bar: "baz",
      qux: "quux"
    });

    functions

    Examples of incorrect code for this rule with the {"functions": "never"} option:

    /*eslint comma-dangle: ["error", {"functions": "never"}]*/
    
    function foo(a, b,) {
    }
    
    foo(a, b,);
    new foo(a, b,);

    Examples of correct code for this rule with the {"functions": "never"} option:

    /*eslint comma-dangle: ["error", {"functions": "never"}]*/
    
    function foo(a, b) {
    }
    
    foo(a, b);
    new foo(a, b);

    Examples of incorrect code for this rule with the {"functions": "always"} option:

    /*eslint comma-dangle: ["error", {"functions": "always"}]*/
    
    function foo(a, b) {
    }
    
    foo(a, b);
    new foo(a, b);

    Examples of correct code for this rule with the {"functions": "always"} option:

    /*eslint comma-dangle: ["error", {"functions": "always"}]*/
    
    function foo(a, b,) {
    }
    
    foo(a, b,);
    new foo(a, b,);

    When Not To Use It

    You can turn this rule off if you are not concerned with dangling commas. Source: http://eslint.org/docs/rules/

    There are no issues that match your filters.

    Category
    Status