Optional chaining with types in Typescript - Time & Space Complexity

Time Complexity: Optional chaining with types

O(d)

Understanding Time Complexity

We want to understand how using optional chaining affects the time it takes to access properties in TypeScript.

Specifically, how does the cost change when we check nested properties safely?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

interface User {
  profile?: {
    address?: {
      city?: string;
    };
  };
}

function getCity(user: User): string | undefined {
  return user.profile?.address?.city;
}
    

This code safely accesses a nested city property using optional chaining to avoid errors if any part is missing.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Property access checks using optional chaining.
• How many times: Each property is checked once in sequence.

How Execution Grows With Input

Each access checks one property. The number of checks grows with how deep the chain is, not with input size.

Chain Depth (d)	Approx. Operations
1 (shallow)	1 property check
10 (deeper chain)	10 property checks
100 (very deep chain)	100 property checks

Pattern observation: The time grows linearly with the depth of the property chain, not with the size of the data.

Final Time Complexity

Time Complexity: O(d)

This means the time to access a nested property grows linearly with the depth of the chain.

Common Mistake

[X] Wrong: "Optional chaining makes property access constant time regardless of depth."

[OK] Correct: Each level must be checked one by one, so deeper chains take more steps.

Interview Connect

Understanding how optional chaining affects access time helps you write safe and efficient code, a skill valued in real projects and interviews.

Self-Check

"What if we replaced optional chaining with a loop that checks properties dynamically? How would the time complexity change?"

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