Optional properties in Typescript - Step-by-Step Execution

Concept Flow - Optional properties

Define interface with optional property

↓

Create object with or without optional property

↓

Access optional property

↓

Check if property exists before use

↓

Use property safely or handle undefined

This flow shows how optional properties in TypeScript interfaces allow objects to have or skip certain properties, and how to safely access them.

Execution Sample

Typescript

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

const user1: User = { name: "Alice" };
const user2: User = { name: "Bob", age: 30 };

console.log(user1.age);
console.log(user2.age);

This code defines a User interface with an optional age property, creates two users (one without age), and logs their ages.

Execution Table

Step	Action	Object State	Property Access	Output
1	Define interface User with optional age	User { name: string; age?: number }	N/A	N/A
2	Create user1 with name only	user1 = { name: "Alice" }	user1.age	undefined
3	Create user2 with name and age	user2 = { name: "Bob", age: 30 }	user2.age	30
4	Log user1.age	user1 = { name: "Alice" }	user1.age	undefined
5	Log user2.age	user2 = { name: "Bob", age: 30 }	user2.age	30

💡 All steps executed; optional property age is undefined for user1 and defined for user2.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
user1	undefined	{ name: "Alice" }	{ name: "Alice" }	{ name: "Alice" }
user2	undefined	undefined	{ name: "Bob", age: 30 }	{ name: "Bob", age: 30 }

Key Moments - 2 Insights

Why does user1.age show undefined instead of an error?

Because age is marked optional with ?, it may be missing. Accessing it returns undefined, not an error, as shown in execution_table step 4.

Can we assign user1.age later even if it was not set initially?

Yes, optional means the property can be missing initially but can be added later. The interface allows it to be undefined or a number.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output when accessing user1.age at step 4?

A undefined

B null

C 0

D Error

💡 Hint

Check the 'Output' column for step 4 in execution_table.

At which step is user2 created with the age property defined?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Action' and 'Object State' columns in execution_table.

If we remove the ? from age in the interface, what would happen when creating user1 without age?

A user1.age would be undefined

B It would cause a TypeScript error

C user1 would have age set to null

D No change, code runs fine

💡 Hint

Optional properties allow missing fields; removing ? makes age required.

Concept Snapshot

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

- Optional properties may be missing
- Accessing missing optional property returns undefined
- Helps create flexible object shapes

Full Transcript

This example shows how TypeScript interfaces can have optional properties using the ? symbol. The User interface has an optional age property. We create two objects: user1 without age and user2 with age. Accessing user1.age returns undefined safely without error. This allows flexible objects where some properties can be missing. The execution table traces each step: defining interface, creating objects, and accessing properties. The variable tracker shows how user1 and user2 change. Key moments clarify why accessing missing optional properties does not cause errors. The quiz tests understanding of optional properties behavior and TypeScript rules.

Practice

1. What does the ? symbol mean when used in a TypeScript interface property like age?: number?

easy

A. The property is required and must always be present.

B. The property is private and cannot be accessed outside the interface.

C. The property is optional and may or may not be present in objects.

D. The property is readonly and cannot be changed after initialization.

Solution

1. Step 1: Understand the meaning of ? in interfaces

   The ? after a property name marks it as optional, meaning it can be missing in objects that implement the interface.

2. Step 2: Compare with other property types

   Required properties must always be present, private and readonly are unrelated concepts.

3. Final Answer:

   The property is optional and may or may not be present in objects. -> Option C

4. Quick Check:

   Optional property = property with ? [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 a default value

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. optional email: string

C. email: string?

D. email: optional string

Solution

1. Step 1: Recall TypeScript optional property syntax

   Optional properties use a ? immediately after the property name, before the colon and type.

2. Step 2: Check each option

   email?: string matches the correct syntax: email?: string. Others are invalid syntax.

3. Final Answer:

   email?: string -> Option A

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
• Missing colon between property name and type

3. Given this interface and object:

interface User {
  id: number;
  name?: string;
}

const user: User = { id: 1 };
console.log(user.name);

What will be the output when running this code?

medium

A. undefined

B. null

C. An error because name is missing

D. Empty string

Solution

1. Step 1: Understand optional property behavior

   The property name is optional and not provided in the object, so it is undefined.

2. Step 2: Check console.log output

   Logging user.name prints undefined because the property is missing, not null or empty string.

3. Final Answer:

   undefined -> Option A

4. Quick Check:

   Missing optional property = undefined [OK]

Hint: Missing optional properties are undefined, not errors [OK]

Common Mistakes:

• Expecting runtime error for missing optional property
• Confusing undefined with null or empty string
• Assuming default values are assigned automatically

4. Identify the error in this TypeScript interface declaration:

interface Product {
  id: number;
  description?: string = "No description";
}

medium

A. The interface keyword is misspelled.

B. The property id must be optional too.

C. The equals sign = should be a colon :.

D. Optional properties cannot have default values in interfaces.

Solution

1. Step 1: Check interface property syntax

   Interfaces only declare types; they cannot assign default values to properties.

2. Step 2: Analyze the error

   The syntax description?: string = "No description" is invalid because default values are not allowed in interfaces.

3. Final Answer:

   Optional properties cannot have default values in interfaces. -> Option D

4. Quick Check:

   Interfaces declare types, no default values allowed [OK]

Hint: Interfaces declare types only, no default values [OK]

Common Mistakes:

• Trying to assign default values inside interfaces
• Confusing interfaces with classes or object literals
• Ignoring TypeScript syntax rules for interfaces

5. You want to create a function that accepts an object with optional middleName property and returns the full name. Which of these implementations correctly handles the optional property without errors?

interface Person {
  firstName: string;
  middleName?: string;
  lastName: string;
}

function getFullName(person: Person): string {
  // Which code below is correct?
}

hard

A. return `${person.firstName} ${person.middleName} ${person.lastName}`;

B. return `${person.firstName} ${person.middleName ?? ''} ${person.lastName}`.trim();

C. return `${person.firstName} ${person.middleName!} ${person.lastName}`;

D. return person.firstName + person.middleName + person.lastName;

Solution

1. Step 1: Understand optional property usage

   The middleName may be undefined, so accessing it directly can cause unwanted 'undefined' in output.

2. Step 2: Evaluate each option

   return `${person.firstName} ${person.middleName} ${person.lastName}`; inserts undefined if missing. return `${person.firstName} ${person.middleName ?? ''} ${person.lastName}`.trim(); uses nullish coalescing ?? to replace undefined with empty string and trims extra spaces. return `${person.firstName} ${person.middleName!} ${person.lastName}`; uses non-null assertion which can cause runtime errors if missing. return person.firstName + person.middleName + person.lastName; concatenates without spaces and can produce 'undefined' string.

3. Final Answer:

   return `${person.firstName} ${person.middleName ?? ''} ${person.lastName}`.trim(); -> Option B

4. Quick Check:

   Use ?? '' to safely handle optional strings [OK]

Hint: Use nullish coalescing (?? '') to handle optional strings safely [OK]

Common Mistakes:

• Directly using optional property without checks
• Using non-null assertion (!) unsafely
• Concatenating without spaces or trimming