Showing 489 of 489 total issues

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

.frame-square, .frame-round {
Severity: Minor
Found in src/pyff/site/static/css/icon.css by csslint

Adjoining classes: .nav-pills.flex-column > .nav-item > .nav-link.active
Open

.nav-pills.flex-column > .nav-item > .nav-link.active,
Severity: Minor
Found in src/pyff/site/static/css/nav.css by csslint

Adjoining classes: .nav-pills.flex-column > .nav-item > .nav-link.active
Open

.nav-pills.flex-column > .nav-item > .nav-link.active,
Severity: Minor
Found in src/pyff/site/static/css/nav.css by csslint

Values of 0 shouldn't have units specified.
Open

    border-radius: 0px;
Severity: Minor
Found in src/pyff/site/static/css/nav.css by csslint

Heading (h3) has already been defined.
Open

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

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

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

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 (<length> | <percentage> | <content-sizing> | auto) but found 'device-width'.</content-sizing></percentage></length>
Open

@-o-viewport        { width: device-width; }
Severity: Minor
Found in src/pyff/site/static/css/style.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

Don't use IDs in selectors.
Open

#map_canvas img { max-width: none; }
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint

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

.footer {
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint

Values of 0 shouldn't have units specified.
Open

    padding-bottom: 0px;
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint

The universal selector (*) is known to be slow.
Open

.google-map-canvas,.google-map-canvas * { box-sizing:content-box; }
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint

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

.tt-suggestion > div {

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

            if (DiscoveryService._incr_use_count(id,lst) == -1) {
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/

Shadowing of global property 'undefined'.
Open

    (function(window, undefined) {
Severity: Minor
Found in src/pyff/site/static/js/ds-client.js by eslint

Disallow Shadowing of Restricted Names (no-shadow-restricted-names)

ES5 §15.1.1 Value Properties of the Global Object (NaN, Infinity, undefined) as well as strict mode restricted identifiers eval and arguments are considered to be restricted names in JavaScript. Defining them to mean something else can have unintended consequences and confuse others reading the code. For example, there's nothing prevent you from writing:

var undefined = "foo";

Then any code used within the same scope would not get the global undefined, but rather the local version with a very different meaning.

Rule Details

Examples of incorrect code for this rule:

/*eslint no-shadow-restricted-names: "error"*/

function NaN(){}

!function(Infinity){};

var undefined;

try {} catch(eval){}

Examples of correct code for this rule:

/*eslint no-shadow-restricted-names: "error"*/

var Object;

function f(a, b){}

Further Reading

Related Rules

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

p {
Severity: Minor
Found in src/pyff/site/static/css/ra21.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

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

Don't use IDs in selectors.
Open

#sp-icon-container {
Severity: Minor
Found in src/pyff/site/static/css/style.css by csslint
Severity
Category
Status
Source
Language