Showing 208 of 208 total issues
Values of 0 shouldn't have units specified. Open
-webkit-box-shadow: 0px 0px 8px 2px rgba(0,0,0,0.3);
- Exclude checks
Use of !important Open
background-color:#AAF7BE !important;
- Exclude checks
Don't use IDs in selectors. Open
#months-select>div>a{
- Exclude checks
Fallback background-color (hex or RGB) should precede RGBA background-color. Open
background-color: rgba(6, 147, 192, 0.64);
- Exclude checks
Adjoining classes: nav.navbar.navbar-default.navbar-fixed-top .navbar-nav > li > a Open
nav.navbar.navbar-default.navbar-fixed-top .navbar-nav>li>a{
- Exclude checks
Use of !important Open
background-color: rgb(253, 255, 252) !important;
- Exclude checks
Missing standard property 'box-shadow' to go along with '-webkit-box-shadow'. Open
-webkit-box-shadow: 0px 0px 8px 2px rgba(100,100,100,0.3);
- Exclude checks
Values of 0 shouldn't have units specified. Open
bottom:0px;
- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
.round-btn{
- Exclude checks
Don't use IDs in selectors. Open
#save-response-btn{
- Exclude checks
Don't use IDs in selectors. Open
#post-input-div{
- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
#post-input-div{
- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
nav.navbar.navbar-default.navbar-fixed-top{
- Exclude checks
Expected '!==' and instead saw '!='. Open
return x.id != post.id;
- Read upRead up
- Exclude checks
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 treatsnull
literals. Possible values:-
always
(default) - Always use === or !==. -
never
- Never use === or !== withnull
. -
ignore
- Do not apply this rule tonull
.
-
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/
Don't use IDs in selectors. Open
#add-btn{
- Exclude checks
Don't use IDs in selectors. Open
#btns-container{
- Exclude checks
Use of !important Open
border-radius:1000px !important;
- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
.admin-controls{
- Exclude checks
Values of 0 shouldn't have units specified. Open
border:0px;
- Exclude checks
Rule doesn't have all its properties in alphabetical order. Open
.gravatar{
- Exclude checks