Bird
Raised Fist0
Typescriptprogramming~5 mins

Optional properties in interfaces in Typescript - Time & Space Complexity

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Time Complexity: Optional properties in interfaces
O(n)
Understanding Time Complexity

We want to see how the time it takes to check optional properties in interfaces changes as the input grows.

How does the program's work increase when more objects with optional properties are checked?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.


interface User {
  id: number;
  name?: string; // optional property
}

function greetUsers(users: User[]) {
  for (const user of users) {
    if (user.name !== undefined) {
      console.log(`Hello, ${user.name}!`);
    } else {
      console.log('Hello, guest!');
    }
  }
}

This code loops through a list of users and greets them by name if available, or as guest if not.

Identify Repeating Operations
  • Primary operation: Looping through each user in the array.
  • How many times: Once for every user in the list.
How Execution Grows With Input

Each user causes one check and one greeting. More users mean more checks and greetings.

Input Size (n)Approx. Operations
1010 greetings and checks
100100 greetings and checks
10001000 greetings and checks

Pattern observation: The work grows directly with the number of users.

Final Time Complexity

Time Complexity: O(n)

This means the time to greet users grows in a straight line as the number of users increases.

Common Mistake

[X] Wrong: "Checking optional properties makes the code slower in a way that depends on how many optional properties there are."

[OK] Correct: The check for an optional property is simple and happens once per user, so it only adds a small constant step per user, not extra loops or nested work.

Interview Connect

Understanding how optional properties affect loops helps you explain how your code scales when handling flexible data shapes, a useful skill in many coding tasks.

Self-Check

What if we added a nested loop inside the greeting to check multiple optional properties? How would the time complexity change?

Practice

(1/5)
1. What does the ? symbol mean when used in a TypeScript interface property like age?: number?
easy
A. The property is readonly and cannot be changed after initialization.
B. The property is required and must always be provided.
C. The property is private and cannot be accessed outside the interface.
D. The property is optional and may be omitted when creating an object.

Solution

  1. Step 1: Understand the ? in interface properties

    The ? after a property name in an interface means that property is optional.

  2. Step 2: Effect on object creation

    This means when creating an object of that interface type, you can omit that property without error.

  3. Final Answer:

    The property is optional and may be omitted when creating an object. -> Option D

  4. Quick Check:

    Optional property = may be omitted [OK]
Hint: Look for ? to spot optional properties quickly [OK]
Common Mistakes:
  • Thinking ? means property is required
  • Confusing optional with readonly or private
  • Assuming optional properties must have default values
2. Which of the following is the correct syntax to declare an optional property email of type string in a TypeScript interface?
easy
A. email: string;
B. email: string?;
C. email?: string;
D. optional email: string;

Solution

  1. Step 1: Recall optional property syntax

    In TypeScript, optional properties use a ? immediately after the property name.

  2. Step 2: Match syntax to options

    Only email?: string; uses email?: string; which is correct syntax for optional property.

  3. Final Answer:

    email?: string; -> Option C

  4. Quick Check:

    Optional property syntax = name? : type [OK]
Hint: Remember: ? goes right after property name [OK]
Common Mistakes:
  • Placing ? after the type instead of property name
  • Using keywords like 'optional' which are invalid
  • Omitting the semicolon but that is less critical
3. Given the interface and object below, what will be the output of console.log(user.age)? 
interface User {
  name: string;
  age?: number;
}
const user: User = { name: "Alice" };
console.log(user.age);
medium
A. Error: Property 'age' is missing
B. undefined
C. null
D. 0

Solution

  1. Step 1: Understand optional property behavior

    The property age is optional and not provided in the object.

  2. Step 2: Check value of missing optional property

    Accessing a missing optional property returns undefined in JavaScript/TypeScript.

  3. Final Answer:

    undefined -> Option B

  4. Quick Check:

    Missing optional property = undefined [OK]
Hint: Missing optional property returns undefined, not error [OK]
Common Mistakes:
  • Expecting runtime error for missing optional property
  • Confusing undefined with null or zero
  • Assuming default values are assigned automatically
4. Identify the error in the following code snippet: 
interface Product {
  id: number;
  description?: string;
}

const item: Product = {
  id: 101,
  description: undefined
};
medium
A. Assigning undefined to an optional property is allowed.
B. Optional properties cannot be assigned undefined explicitly.
C. Missing semicolon after interface declaration.
D. Property 'id' should be optional too.

Solution

  1. Step 1: Check assignment to optional property

    Optional properties can be omitted or explicitly assigned undefined.

  2. Step 2: Validate code correctness

    Assigning undefined to description is valid and causes no error.

  3. Final Answer:

    Assigning undefined to an optional property is allowed. -> Option A

  4. Quick Check:

    Optional property can be undefined explicitly [OK]
Hint: Optional properties accept undefined explicitly without error [OK]
Common Mistakes:
  • Thinking undefined assignment causes error
  • Confusing optional with required properties
  • Ignoring that missing semicolon is not an error here
5. You have this interface: 
interface Config {
  url: string;
  timeout?: number;
  retries?: number;
}
Which of the following objects correctly implements Config with only url provided and no errors?
hard
A. { url: "http://example.com", timeout: undefined, retries: undefined }
B. { url: "http://example.com", timeout: null }
C. { url: "http://example.com", timeout: 0, retries: 3 }
D. { timeout: 1000, retries: 3 }

Solution

  1. Step 1: Check required properties

    The url property is required and must be present.

  2. Step 2: Validate optional properties usage

    Optional properties can be omitted or set to undefined without error.

  3. Step 3: Analyze each option

    { url: "http://example.com", timeout: undefined, retries: undefined } has url and optional properties set to undefined, which is valid.
    { url: "http://example.com", timeout: null } uses null which is not assignable to number.
    { url: "http://example.com", timeout: 0, retries: 3 } includes optional properties but that is allowed, but question asks for only url provided.
    { timeout: 1000, retries: 3 } misses required url property.

  4. Final Answer:

    { url: "http://example.com", timeout: undefined, retries: undefined } -> Option A

  5. Quick Check:

    Required present, optional can be undefined or omitted [OK]
Hint: Required must exist; optional can be undefined or omitted [OK]
Common Mistakes:
  • Using null for number type optional properties
  • Omitting required properties
  • Assuming optional must be omitted, not undefined
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard