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.
Inspection options
Option | Type | Default |
|---|---|---|
Highlight usages of '==' and '!=' | Dropdown | All except when comparing with null or typeof |
Inspection Details | |
|---|---|
Available in: | AppCode 2023.3, CLion 2023.3, GoLand 2023.3, IntelliJ IDEA 2023.3, JetBrains Rider 2023.1, PhpStorm 2023.3, PyCharm 2023.3, Qodana for .NET 2023.1, Qodana for JS 2023.3, Qodana for JVM 2023.3, Qodana for PHP 2023.3, Qodana for Ruby 2023.3, RubyMine 2023.3, WebStorm 2023.3 |
Plugin: | JavaScript and TypeScript, 233.SNAPSHOT |