Optional properties in interfaces in Typescript - Step-by-Step Execution

Concept Flow - Optional properties in interfaces

Define Interface with Optional Property

↓

Create Object with or without Optional Property

↓

Access Property

↓

Property Exists

↓

Use Value

This flow shows how an interface with optional properties allows objects to include or omit those properties, and how code handles their presence or absence.

Execution Sample

Typescript

interface Person {
  name: string;
  age?: number;
}

const p1: Person = { name: "Alice" };
const p2: Person = { name: "Bob", age: 30 };

Defines a Person interface with an optional age property, then creates two objects: one without age and one with age.

Execution Table

Step	Action	Object Created	Property 'age' Present?	Value of 'age'
1	Create p1 with only name	{ name: "Alice" }	No	undefined
2	Access p1.age	Same as above	No	undefined
3	Create p2 with name and age	{ name: "Bob", age: 30 }	Yes	30
4	Access p2.age	Same as above	Yes	30

💡 All objects created successfully; optional property 'age' may be missing or present.

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
p1	undefined	{ name: "Alice" }	{ name: "Alice" }	{ name: "Alice" }
p2	undefined	undefined	{ name: "Bob", age: 30 }	{ name: "Bob", age: 30 }

Key Moments - 2 Insights

Why can we create p1 without the 'age' property even though it's in the interface?

Because 'age' is marked optional with '?', it means objects can omit it. The execution_table rows 1 and 2 show p1 created without 'age' and accessing it returns undefined.

What happens if we try to access an optional property that is missing?

Accessing a missing optional property returns undefined, as shown in execution_table row 2 when accessing p1.age.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of p1.age after step 2?

A 0

B undefined

C null

D 30

💡 Hint

Check the 'Value of age' column in row 2 of the execution_table.

At which step does the object have the 'age' property present?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Property age Present?' column in the execution_table.

If we remove the '?' from 'age' in the interface, what would happen when creating p1?

A p1 creation would cause a type error

B p1 would be created successfully without age

C p1.age would be undefined but no error

D p1.age would default to 0

💡 Hint

Optional properties allow omission; removing '?' makes 'age' required.

Concept Snapshot

interface Person {
  name: string;
  age?: number; // '?' means optional
}

- Objects can omit optional properties.
- Accessing missing optional properties returns undefined.
- Helps flexible object shapes without errors.

Full Transcript

This example shows how to use optional properties in TypeScript interfaces. The interface Person has a required 'name' and an optional 'age'. We create two objects: p1 without 'age' and p2 with 'age'. Accessing p1.age returns undefined because it is missing. Optional properties allow objects to be flexible and avoid errors when some data is not present.

Practice

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