Avoid non-null assertion in confusing locations
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。
ID: typescript-code-style/no-confusing-non-null-assertion
Language: TypeScript
Severity: Warning
Category: Error Prone
Description
Using a non-null assertion (!) next to an assign or equals check (= or == or ===) could be confusing.
Non-Compliant Code Examples
a! == b;
a! === b;
a + b! == c;
(obj = new new OuterObj().InnerObj).Name! == c;
(a==b)! ==c;
a! = b;
(obj = new new OuterObj().InnerObj).Name! = c;
(a=b)! =c;
Compliant Code Examples
a == b!;
a = b!;
a !== b;
a != b;
(a + b!) == c;
(a + b!) = c;
Seamless integrations. Try Datadog Code Analysis
