Avoid non-null assertion in confusing locations

Docs > Code Analysis > Static Analysis Rules > Avoid non-null assertion in confusing locations

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Metadata

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;

How to use this rule

1
2
rulesets:
  - typescript-code-style     # Rules to enforce TypeScript code style.

Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Analysis scans to your CI pipelines
Get feedback on your code

For more information, please read the Code Analysis documentation

VS Code Extension

Identify code vulnerabilities directly in your
VS Code editor

JetBrains Plugin

Identify code vulnerabilities directly in
JetBrains products