Sign upLogin

renyard/validity

View on GitHub
Star
src/validity.js

Summary

Maintainability
A
1 hr
Test Coverage

Function '_logMessages' has a complexity of 12.
Open

    function _logMessages(response) {
Severity: Minor
Found in src/validity.js by eslint

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 _logMessages has 46 lines of code (exceeds 25 allowed). Consider refactoring.
Open

    function _logMessages(response) {
        var messages,
            message,
            line,
            errorCount = response.errorCount,
Severity: Minor
Found in src/validity.js - About 1 hr to fix

    Infix operators must be spaced.
    Open

                        (errorCount > 1?'s':'') +
    Severity: Minor
    Found in src/validity.js by eslint

    require spacing around infix operators (space-infix-ops)

    While formatting preferences are very personal, a number of style guides require spaces around operators, such as:

    var sum = 1 + 2;

    The proponents of these extra spaces believe it make the code easier to read and can more easily highlight potential errors, such as:

    var sum = i+++2;

    While this is valid JavaScript syntax, it is hard to determine what the author intended.

    Rule Details

    This rule is aimed at ensuring there are spaces around infix operators.

    Options

    This rule accepts a single options argument with the following defaults:

    "space-infix-ops": ["error", {"int32Hint": false}]

    int32Hint

    Set the int32Hint option to true (default is false) to allow write a|0 without space.

    var foo = bar|0; // `foo` is forced to be signed 32 bit integer

    Examples of incorrect code for this rule:

    /*eslint space-infix-ops: "error"*/
/*eslint-env es6*/

a+b

a+ b

a +b

a?b:c

const a={b:1};

var {a=0}=bar;

function foo(a=0) { }

    Examples of correct code for this rule:

    /*eslint space-infix-ops: "error"*/
/*eslint-env es6*/

a + b

a       + b

a ? b : c

const a = {b:1};

var {a = 0} = bar;

function foo(a = 0) { }

    Source: http://eslint.org/docs/rules/

    Infix operators must be spaced.
    Open

                        (warningCount > 1?'s':'') +
    Severity: Minor
    Found in src/validity.js by eslint

    require spacing around infix operators (space-infix-ops)

    While formatting preferences are very personal, a number of style guides require spaces around operators, such as:

    var sum = 1 + 2;

    The proponents of these extra spaces believe it make the code easier to read and can more easily highlight potential errors, such as:

    var sum = i+++2;

    While this is valid JavaScript syntax, it is hard to determine what the author intended.

    Rule Details

    This rule is aimed at ensuring there are spaces around infix operators.

    Options

    This rule accepts a single options argument with the following defaults:

    "space-infix-ops": ["error", {"int32Hint": false}]

    int32Hint

    Set the int32Hint option to true (default is false) to allow write a|0 without space.

    var foo = bar|0; // `foo` is forced to be signed 32 bit integer

    Examples of incorrect code for this rule:

    /*eslint space-infix-ops: "error"*/
/*eslint-env es6*/

a+b

a+ b

a +b

a?b:c

const a={b:1};

var {a=0}=bar;

function foo(a=0) { }

    Examples of correct code for this rule:

    /*eslint space-infix-ops: "error"*/
/*eslint-env es6*/

a + b

a       + b

a ? b : c

const a = {b:1};

var {a = 0} = bar;

function foo(a = 0) { }

    Source: http://eslint.org/docs/rules/

    Infix operators must be spaced.
    Open

                        (infoCount > 1?'s':'') +
    Severity: Minor
    Found in src/validity.js by eslint

    require spacing around infix operators (space-infix-ops)

    While formatting preferences are very personal, a number of style guides require spaces around operators, such as:

    var sum = 1 + 2;

    The proponents of these extra spaces believe it make the code easier to read and can more easily highlight potential errors, such as:

    var sum = i+++2;

    While this is valid JavaScript syntax, it is hard to determine what the author intended.

    Rule Details

    This rule is aimed at ensuring there are spaces around infix operators.

    Options

    This rule accepts a single options argument with the following defaults:

    "space-infix-ops": ["error", {"int32Hint": false}]

    int32Hint

    Set the int32Hint option to true (default is false) to allow write a|0 without space.

    var foo = bar|0; // `foo` is forced to be signed 32 bit integer

    Examples of incorrect code for this rule:

    /*eslint space-infix-ops: "error"*/
/*eslint-env es6*/

a+b

a+ b

a +b

a?b:c

const a={b:1};

var {a=0}=bar;

function foo(a=0) { }

    Examples of correct code for this rule:

    /*eslint space-infix-ops: "error"*/
/*eslint-env es6*/

a + b

a       + b

a ? b : c

const a = {b:1};

var {a = 0} = bar;

function foo(a = 0) { }

    Source: http://eslint.org/docs/rules/

    Infix operators must be spaced.
    Open

                        (line > 0?'line ' + line + ': ':'') +
    Severity: Minor
    Found in src/validity.js by eslint

    require spacing around infix operators (space-infix-ops)

    While formatting preferences are very personal, a number of style guides require spaces around operators, such as:

    var sum = 1 + 2;

    The proponents of these extra spaces believe it make the code easier to read and can more easily highlight potential errors, such as:

    var sum = i+++2;

    While this is valid JavaScript syntax, it is hard to determine what the author intended.

    Rule Details

    This rule is aimed at ensuring there are spaces around infix operators.

    Options

    This rule accepts a single options argument with the following defaults:

    "space-infix-ops": ["error", {"int32Hint": false}]

    int32Hint

    Set the int32Hint option to true (default is false) to allow write a|0 without space.

    var foo = bar|0; // `foo` is forced to be signed 32 bit integer

    Examples of incorrect code for this rule:

    /*eslint space-infix-ops: "error"*/
/*eslint-env es6*/

a+b

a+ b

a +b

a?b:c

const a={b:1};

var {a=0}=bar;

function foo(a=0) { }

    Examples of correct code for this rule:

    /*eslint space-infix-ops: "error"*/
/*eslint-env es6*/

a + b

a       + b

a ? b : c

const a = {b:1};

var {a = 0} = bar;

function foo(a = 0) { }

    Source: http://eslint.org/docs/rules/

    There are no issues that match your filters.

    Category
    Status