noNonNullAssertedOptionalChain

JavaScript (and super languages)

Summary

Rule available since: v2.1.4
Diagnostic Category: lint/suspicious/noNonNullAssertedOptionalChain
This rule is recommended, which means is enabled by default.
This rule doesn’t have a fix.
The default severity of this rule is error.
Sources:
- Same as @typescript-eslint/no-non-null-asserted-optional-chain

How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "suspicious": {
5
        "noNonNullAssertedOptionalChain": "error"
6
      }
7
    }
8
  }
9
}

Description

Disallow non-null assertions after optional chaining expressions.

Optional chaining (?.) is designed to return undefined if the object is null or undefined. Using a non-null assertion (!) immediately after optional chaining defeats the purpose of optional chaining and can lead to runtime errors.

Examples

Invalid

1
obj?.prop!;

code-block.ts:1:1 lint/suspicious/noNonNullAssertedOptionalChain ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Forbidden non-null assertion after optional chaining.
  
  > 1 │ obj?.prop!;
      │ ^^^^^^^^^^
    2 │ 
  
  ℹ Optional chaining already handles nullish values. Using non-null assertion defeats its purpose and may cause runtime errors.
  
  ℹ Consider using the nullish coalescing operator ?? or optional chaining throughout the chain instead.

1
obj?.method()!.prop;

code-block.ts:1:1 lint/suspicious/noNonNullAssertedOptionalChain ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Forbidden non-null assertion after optional chaining.
  
  > 1 │ obj?.method()!.prop;
      │ ^^^^^^^^^^^^^^
    2 │ 
  
  ℹ Optional chaining already handles nullish values. Using non-null assertion defeats its purpose and may cause runtime errors.
  
  ℹ Consider using the nullish coalescing operator ?? or optional chaining throughout the chain instead.

1
obj?.[key]!.method();

code-block.ts:1:1 lint/suspicious/noNonNullAssertedOptionalChain ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ✖ Forbidden non-null assertion after optional chaining.
  
  > 1 │ obj?.[key]!.method();
      │ ^^^^^^^^^^^
    2 │ 
  
  ℹ Optional chaining already handles nullish values. Using non-null assertion defeats its purpose and may cause runtime errors.
  
  ℹ Consider using the nullish coalescing operator ?? or optional chaining throughout the chain instead.

Valid

1
obj?.prop;

1
obj!.prop?.method();

1
obj?.prop ?? defaultValue;