Showing 497 of 497 total issues

Rule doesn't have all its properties in alphabetical order.
Open

.form-control:focus {
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Use of !important
Open

    max-width: 20% !important;
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint

Don't use IDs in selectors.
Open

#pyff-saved-choices {
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint

Fallback color (hex or RGB) should precede RGBA color.
Open

    color: rgba(0,0,0,0.65);
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Rule doesn't have all its properties in alphabetical order.
Open

.institution {
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Rule doesn't have all its properties in alphabetical order.
Open

.searchaux {
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Heading (h3) has already been defined.
Open

.content h1, h2, h3 {
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint

Unknown @ rule: @-webkit-viewport.
Open

@-webkit-viewport   { width: device-width; }
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint

Fallback color (hex or RGB) should precede RGBA color.
Open

    color: rgba(0,0,0,0.65);
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Expected '===' and instead saw '=='.
Open

                if (last_refresh == -1 || last_refresh + cache_time < DiscoveryService._now()) {
Severity: Minor
Found in src/pyff/site/static/js/ds-client.js by eslint

Require === and !== (eqeqeq)

It is considered good practice to use the type-safe equality operators === and !== instead of their regular counterparts == and !=.

The reason for this is that == and != do type coercion which follows the rather obscure Abstract Equality Comparison Algorithm. For instance, the following statements are all considered true:

  • [] == false
  • [] == ![]
  • 3 == "03"

If one of those occurs in an innocent-looking statement such as a == b the actual problem is very difficult to spot.

Rule Details

This rule is aimed at eliminating the type-unsafe equality operators.

Examples of incorrect code for this rule:

/*eslint eqeqeq: "error"*/

if (x == 42) { }

if ("" == text) { }

if (obj.getStuff() != undefined) { }

The --fix option on the command line automatically fixes some problems reported by this rule. A problem is only fixed if one of the operands is a typeof expression, or if both operands are literals with the same type.

Options

always

The "always" option (default) enforces the use of === and !== in every situation (except when you opt-in to more specific handling of null [see below]).

Examples of incorrect code for the "always" option:

/*eslint eqeqeq: ["error", "always"]*/

a == b
foo == true
bananas != 1
value == undefined
typeof foo == 'undefined'
'hello' != 'world'
0 == 0
true == true
foo == null

Examples of correct code for the "always" option:

/*eslint eqeqeq: ["error", "always"]*/

a === b
foo === true
bananas !== 1
value === undefined
typeof foo === 'undefined'
'hello' !== 'world'
0 === 0
true === true
foo === null

This rule optionally takes a second argument, which should be an object with the following supported properties:

  • "null": Customize how this rule treats null literals. Possible values:
    • always (default) - Always use === or !==.
    • never - Never use === or !== with null.
    • ignore - Do not apply this rule to null.

smart

The "smart" option enforces the use of === and !== except for these cases:

  • Comparing two literal values
  • Evaluating the value of typeof
  • Comparing against null

Examples of incorrect code for the "smart" option:

/*eslint eqeqeq: ["error", "smart"]*/

// comparing two variables requires ===
a == b

// only one side is a literal
foo == true
bananas != 1

// comparing to undefined requires ===
value == undefined

Examples of correct code for the "smart" option:

/*eslint eqeqeq: ["error", "smart"]*/

typeof foo == 'undefined'
'hello' != 'world'
0 == 0
true == true
foo == null

allow-null

Deprecated: Instead of using this option use "always" and pass a "null" option property with value "ignore". This will tell eslint to always enforce strict equality except when comparing with the null literal.

["error", "always", {"null": "ignore"}]

When Not To Use It

If you don't want to enforce a style for using equality operators, then it's safe to disable this rule. Source: http://eslint.org/docs/rules/

Expected (<font-weight>) but found '2rem'.</font-weight>
Open

    font-weight: 2rem;
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Expected '===' and instead saw '=='.
Open

            if (list[i].entity.entity_id == entity_id || list[i].entity.entityID == entity_id) {
Severity: Minor
Found in src/pyff/site/static/js/ds-client.js by eslint

Require === and !== (eqeqeq)

It is considered good practice to use the type-safe equality operators === and !== instead of their regular counterparts == and !=.

The reason for this is that == and != do type coercion which follows the rather obscure Abstract Equality Comparison Algorithm. For instance, the following statements are all considered true:

  • [] == false
  • [] == ![]
  • 3 == "03"

If one of those occurs in an innocent-looking statement such as a == b the actual problem is very difficult to spot.

Rule Details

This rule is aimed at eliminating the type-unsafe equality operators.

Examples of incorrect code for this rule:

/*eslint eqeqeq: "error"*/

if (x == 42) { }

if ("" == text) { }

if (obj.getStuff() != undefined) { }

The --fix option on the command line automatically fixes some problems reported by this rule. A problem is only fixed if one of the operands is a typeof expression, or if both operands are literals with the same type.

Options

always

The "always" option (default) enforces the use of === and !== in every situation (except when you opt-in to more specific handling of null [see below]).

Examples of incorrect code for the "always" option:

/*eslint eqeqeq: ["error", "always"]*/

a == b
foo == true
bananas != 1
value == undefined
typeof foo == 'undefined'
'hello' != 'world'
0 == 0
true == true
foo == null

Examples of correct code for the "always" option:

/*eslint eqeqeq: ["error", "always"]*/

a === b
foo === true
bananas !== 1
value === undefined
typeof foo === 'undefined'
'hello' !== 'world'
0 === 0
true === true
foo === null

This rule optionally takes a second argument, which should be an object with the following supported properties:

  • "null": Customize how this rule treats null literals. Possible values:
    • always (default) - Always use === or !==.
    • never - Never use === or !== with null.
    • ignore - Do not apply this rule to null.

smart

The "smart" option enforces the use of === and !== except for these cases:

  • Comparing two literal values
  • Evaluating the value of typeof
  • Comparing against null

Examples of incorrect code for the "smart" option:

/*eslint eqeqeq: ["error", "smart"]*/

// comparing two variables requires ===
a == b

// only one side is a literal
foo == true
bananas != 1

// comparing to undefined requires ===
value == undefined

Examples of correct code for the "smart" option:

/*eslint eqeqeq: ["error", "smart"]*/

typeof foo == 'undefined'
'hello' != 'world'
0 == 0
true == true
foo == null

allow-null

Deprecated: Instead of using this option use "always" and pass a "null" option property with value "ignore". This will tell eslint to always enforce strict equality except when comparing with the null literal.

["error", "always", {"null": "ignore"}]

When Not To Use It

If you don't want to enforce a style for using equality operators, then it's safe to disable this rule. Source: http://eslint.org/docs/rules/

Fallback background-color (hex or RGB) should precede RGBA background-color.
Open

    background-color: rgba(0,0,0,.0);
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Expected '!==' and instead saw '!='.
Open

                return item.entity.entity_id != id && item.entity.entityID != id;
Severity: Minor
Found in src/pyff/site/static/js/ds-client.js by eslint

Require === and !== (eqeqeq)

It is considered good practice to use the type-safe equality operators === and !== instead of their regular counterparts == and !=.

The reason for this is that == and != do type coercion which follows the rather obscure Abstract Equality Comparison Algorithm. For instance, the following statements are all considered true:

  • [] == false
  • [] == ![]
  • 3 == "03"

If one of those occurs in an innocent-looking statement such as a == b the actual problem is very difficult to spot.

Rule Details

This rule is aimed at eliminating the type-unsafe equality operators.

Examples of incorrect code for this rule:

/*eslint eqeqeq: "error"*/

if (x == 42) { }

if ("" == text) { }

if (obj.getStuff() != undefined) { }

The --fix option on the command line automatically fixes some problems reported by this rule. A problem is only fixed if one of the operands is a typeof expression, or if both operands are literals with the same type.

Options

always

The "always" option (default) enforces the use of === and !== in every situation (except when you opt-in to more specific handling of null [see below]).

Examples of incorrect code for the "always" option:

/*eslint eqeqeq: ["error", "always"]*/

a == b
foo == true
bananas != 1
value == undefined
typeof foo == 'undefined'
'hello' != 'world'
0 == 0
true == true
foo == null

Examples of correct code for the "always" option:

/*eslint eqeqeq: ["error", "always"]*/

a === b
foo === true
bananas !== 1
value === undefined
typeof foo === 'undefined'
'hello' !== 'world'
0 === 0
true === true
foo === null

This rule optionally takes a second argument, which should be an object with the following supported properties:

  • "null": Customize how this rule treats null literals. Possible values:
    • always (default) - Always use === or !==.
    • never - Never use === or !== with null.
    • ignore - Do not apply this rule to null.

smart

The "smart" option enforces the use of === and !== except for these cases:

  • Comparing two literal values
  • Evaluating the value of typeof
  • Comparing against null

Examples of incorrect code for the "smart" option:

/*eslint eqeqeq: ["error", "smart"]*/

// comparing two variables requires ===
a == b

// only one side is a literal
foo == true
bananas != 1

// comparing to undefined requires ===
value == undefined

Examples of correct code for the "smart" option:

/*eslint eqeqeq: ["error", "smart"]*/

typeof foo == 'undefined'
'hello' != 'world'
0 == 0
true == true
foo == null

allow-null

Deprecated: Instead of using this option use "always" and pass a "null" option property with value "ignore". This will tell eslint to always enforce strict equality except when comparing with the null literal.

["error", "always", {"null": "ignore"}]

When Not To Use It

If you don't want to enforce a style for using equality operators, then it's safe to disable this rule. Source: http://eslint.org/docs/rules/

Element (div.cancel) is overqualified, just use .cancel without element name.
Open

div.cancel {
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Using width with padding-left can sometimes make elements larger than you expect.
Open

.sp-thumbnail {width: 100px; margin: 0 0; padding-left: 5px;}
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint

Values of 0 shouldn't have units specified.
Open

    -webkit-box-shadow: 0px 2px 2px rgba(0, 0, 0, 0.3);
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

The property -ms-box-flex is compatible with -webkit-box-flex and should be included as well.
Open

    -webkit-box-flex: 1;
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Rule doesn't have all its properties in alphabetical order.
Open

.card-block {
Severity: Minor
Found in src/pyff/site/static/css/ra21.css by csslint

Rule doesn't have all its properties in alphabetical order.
Open

.content h1, h2, h3 {
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint
Severity
Category
Status
Source
Language