Expected '===' and instead saw '==' eqeqeq

Question

if (customer === "new") {
  //run code
} else {
}

When I run this condition it run my code while actually I have string value in customer "customername" and comparing with sring "new" which is not equal as ("customername" != "new") it should not run the code while comparing. I found to using === equal will check type if type is same it will pass true so == is the option to check the value but I am facing erro on using ==.

Expected '===' and instead saw '=='  eqeqeq

`I found to using === equal will check type if type is same it will pass true` It checks the type __and__ the value. — tkausl, Dec 13 '19 at 16:14
Using `===` checks type **in addition** to the value, meaning `1 == '1'` is true, but `1 === '1'` is false. — Karl-André Gagnon, Dec 13 '19 at 16:14
That's not an "error", it's a linting rule. If you don't want this linting rule, change your linter configuration. Personally I *wouldn't* change the linter rule, but there are, I suppose, legitimate reasons for using `==` in some circumstances. (Very few.) — Dave Newton, Dec 13 '19 at 16:16
Maybe I'm missing something, but I don't see a question here. — CollinD, Dec 13 '19 at 16:16

score 4 · Answer 1 · answered Dec 13 '19 at 16:16

I think you are using JSHint, the "eqeqeq" is an option to ensure the use of strict equality operators.

From here:

The JSHint eqeqeq option is used to prohibit the use of the equals operator == and the does-not-equal operator !=. This enforces the use of the strict equality operators (=== and !== instead). The strict equality operators differ from their non-strict counterparts by first comparing the type of each operand, rather than attempting to coerce them to a common type. In the following example we make use of the non-strict equality operator to check whether a value is either null or undefined

Thanks @Andrea It help me to understand the actual difference stay blessed. — Developer, Dec 13 '19 at 16:27

Expected '===' and instead saw '==' eqeqeq

1 Answers1