Optional chaining with types in Typescript

Introduction

Optional chaining helps you safely access properties or call functions on objects that might be null or undefined. It prevents errors when something is missing.

When you want to get a property from an object that might not exist.

When calling a function that might not be defined on an object.

When working with data from APIs where some fields can be missing.

When accessing nested properties where any level might be undefined.

When you want to avoid writing many checks for <code>null</code> or <code>undefined</code>.

Syntax

Typescript

interface User {
  name?: string;
  address?: {
    street?: string;
    city?: string;
  };
  getAge?: () => number;
}

const user: User = {};

// Access property safely
const street = user.address?.street;

// Call function safely
const age = user.getAge?.();

The ?. operator checks if the value before it is null or undefined. If yes, it stops and returns undefined instead of throwing an error.

Optional chaining works with properties, methods, and array elements.

Examples

Accessing a missing nested property returns undefined instead of error.

Typescript

const user = { name: "Alice" };
console.log(user.address?.street); // undefined

Calling a method safely when it exists.

Typescript

const user = { getAge: () => 30 };
console.log(user.getAge?.()); // 30

Calling a missing method returns undefined safely.

Typescript

const user = {};
console.log(user.getAge?.()); // undefined

Optional chaining works with array elements that might be null.

Typescript

const users = [{ name: "Bob" }, null];
console.log(users[1]?.name); // undefined

Sample Program

This program shows how optional chaining safely accesses properties and methods on two users. The first user has all info, the second is missing some.

Typescript

interface User {
  name?: string;
  address?: {
    street?: string;
    city?: string;
  };
  getAge?: () => number;
}

const user1: User = {
  name: "John",
  address: { street: "Main St", city: "Townsville" },
  getAge: () => 25
};

const user2: User = {
  name: "Jane"
};

function printUserInfo(user: User) {
  console.log(`Name: ${user.name ?? "Unknown"}`);
  console.log(`Street: ${user.address?.street ?? "No street info"}`);
  console.log(`Age: ${user.getAge?.() ?? "Age not available"}`);
}

console.log("User 1 info:");
printUserInfo(user1);

console.log("\nUser 2 info:");
printUserInfo(user2);

Important Notes

Time complexity is the same as normal property access, just a small check added.

Optional chaining returns undefined if the value before ?. is null or undefined.

Common mistake: forgetting that optional chaining returns undefined, so you might need to handle that case.

Use optional chaining when you expect some data might be missing, instead of writing many if checks.

Summary

Optional chaining ?. helps safely access properties or call methods on objects that might be missing.

It prevents runtime errors by returning undefined if something is null or undefined.

Use it to write cleaner and safer code when working with uncertain data.

Practice

1. What does the optional chaining operator ?. do in TypeScript?

easy

A. It forces a property to be non-nullable.

B. It throws an error if the property does not exist.

C. It converts a value to a boolean.

D. It safely accesses a property or method, returning undefined if the value is null or undefined.

Solution

1. Step 1: Understand optional chaining purpose

   Optional chaining ?. allows safe access to nested properties or methods without causing runtime errors if the object is null or undefined.

2. Step 2: Identify behavior on null or undefined

   If the value before ?. is null or undefined, it returns undefined instead of throwing an error.

3. Final Answer:

   It safely accesses a property or method, returning undefined if the value is null or undefined. -> Option D

4. Quick Check:

   Optional chaining = safe access without error [OK]

Hint: Optional chaining returns undefined if value is null or undefined [OK]

Common Mistakes:

• Thinking it throws an error on missing property
• Confusing it with non-null assertion operator
• Assuming it converts values to boolean

2. Which of the following is the correct syntax to safely access the property name of an object user using optional chaining?

easy

A. user?.name()

B. user?.name

C. user?.[name]

D. user?.name?

Solution

1. Step 1: Review optional chaining syntax for properties

   The correct syntax to access a property safely is object?.property.

2. Step 2: Check each option

   user?.name uses user?.name which is correct. user?.[name] uses brackets incorrectly. user?.name() treats name as a method call. user?.name? has invalid syntax.

3. Final Answer:

   user?.name -> Option B

4. Quick Check:

   Property access with ?. = user?.name [OK]

Hint: Use ?. before property name without parentheses for safe access [OK]

Common Mistakes:

• Adding parentheses when accessing properties
• Using brackets incorrectly with optional chaining
• Placing ? after property name

3. Consider the following TypeScript code:

type User = { profile?: { age?: number } };
const user: User = {};
const age = user.profile?.age ?? 30;
console.log(age);

What will be the output?

medium

A. 30

B. null

C. Error at runtime

D. undefined

Solution

1. Step 1: Analyze optional chaining and nullish coalescing

   The expression user.profile?.age safely tries to access age. Since profile is undefined, this returns undefined.

2. Step 2: Apply nullish coalescing operator

   The ?? operator returns the right side value 30 because the left side is undefined.

3. Final Answer:

   30 -> Option A

4. Quick Check:

   undefined ?? 30 = 30 [OK]

Hint: ?. returns undefined if missing; ?? provides default value [OK]

Common Mistakes:

• Expecting undefined instead of default value
• Confusing ?? with || operator
• Assuming runtime error on missing property

4. Identify the error in this TypeScript code snippet:

interface Data {
  info?: {
    value: number;
  };
}

const data: Data = {};
const val = data?.info.value;

medium

A. No error, code works fine

B. Runtime error: accessing property of undefined

C. Type error: missing optional chaining before 'value'

D. Syntax error: optional chaining used incorrectly on data

Solution

1. Step 1: Check optional chaining usage

   The code uses data?.info.value. Optional chaining is applied only on data, but info can be undefined.

2. Step 2: Identify missing optional chaining

   Accessing info.value without optional chaining can cause a runtime error if info is undefined. It should be data.info?.value or data?.info?.value.

3. Final Answer:

   Type error: missing optional chaining before 'value' -> Option C

4. Quick Check:

   Optional chaining needed before 'value' to avoid error [OK]

Hint: Chain ?. for each possibly undefined property [OK]

Common Mistakes:

• Applying ?. only once for nested properties
• Assuming optional chaining on parent covers all children
• Ignoring possible undefined intermediate objects

5. Given this nested object type and variable:

type Config = {
  settings?: {
    theme?: {
      color?: string;
    };
  };
};

const config: Config = {};

Which expression safely accesses the color property and provides a default of 'blue' if missing?

hard

A. config?.settings?.theme?.color ?? 'blue'

B. config.settings.theme.color || 'blue'

C. config.settings?.theme.color ?? 'blue'

D. config?.settings.theme?.color || 'blue'

Solution

1. Step 1: Use optional chaining for all nested optional properties

   Since settings, theme, and color are optional, use ?. at each level: config?.settings?.theme?.color.

2. Step 2: Use nullish coalescing for default value

   Use ?? 'blue' to provide default only if the value is null or undefined, avoiding falsey value issues.

3. Final Answer:

   config?.settings?.theme?.color ?? 'blue' -> Option A

4. Quick Check:

   Chain ?. and use ?? for default [OK]

Hint: Chain ?. for each optional and use ?? for default [OK]

Common Mistakes:

• Using || which treats empty string as false
• Missing optional chaining on some nested properties
• Mixing ?. and non-optional access incorrectly