Equality operator may cause type coercion
Reports a usage of equality operators may cause unexpected type coercions. Suggests replacing == or != equality operators with type-safe === or !== operators.
Depending on the option selected, one of the following cases will be reported:
All usages of
==and!=operators.All usages except comparison with null. Some code styles allow using
x == nullas a replacement forx === null || x === undefined.Only suspicious expressions, such as:
==or!=comparisons with0,'',null,true,false, orundefined.
Locating this inspection
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
EqualityComparisonWithCoercionJS- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
Inspection ID: JSEqualityComparisonWithCoercion.TS
Inspection options
Here you can find the description of settings available for the Equality operator may cause type coercion inspection, and the reference of their default values.
- Highlight usages of '==' and '!='
Option ID:
mySeverityDefault value:
All except when comparing with null or typeofOther available settings:
All
Only suspicious expressions
Suppressing Inspection
You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: | CLion 2025.2, GoLand 2025.2, IntelliJ IDEA 2025.2, JetBrains Rider 2025.2, PhpStorm 2025.2, PyCharm 2025.2, Qodana for .NET 2025.2, Qodana for Go 2025.2, Qodana for JS 2025.2, Qodana for JVM 2025.2, Qodana for PHP 2025.2, Qodana for Ruby 2025.2, RubyMine 2025.2, WebStorm 2025.2 |