Type-safe builder pattern in Typescript - Time & Space Complexity

Time Complexity: Type-safe builder pattern

O(n)

Understanding Time Complexity

We want to understand how the time it takes to build an object grows as we add more steps in a type-safe builder pattern.

How does the number of builder method calls affect the total work done?

Scenario Under Consideration

Analyze the time complexity of the following TypeScript builder pattern code.

class Builder {
  private parts: string[] = [];

  addPart(part: string): this {
    this.parts.push(part);
    return this;
  }

  build(): string {
    return this.parts.join(", ");
  }
}
    

This code builds a string by adding parts one by one, then joining them all at the end.

Identify Repeating Operations

Look for loops or repeated work in the builder.

• Primary operation: Adding parts to an array and joining them.
• How many times: Each addPart call adds one element; build joins all parts once.

How Execution Grows With Input

As you add more parts, the work to join them grows with the number of parts.

Input Size (n)	Approx. Operations
10	Adding 10 parts + joining 10 parts
100	Adding 100 parts + joining 100 parts
1000	Adding 1000 parts + joining 1000 parts

Pattern observation: The joining step grows linearly with the number of parts added.

Final Time Complexity

Time Complexity: O(n)

This means the total work grows in a straight line as you add more parts to the builder.

Common Mistake

[X] Wrong: "Each addPart call does a lot of work, so the builder is slow."

[OK] Correct: Each addPart just adds one item quickly; the main work happens once when build() joins all parts.

Interview Connect

Understanding how builder patterns scale helps you design clean and efficient code, a skill valued in many coding challenges.

Self-Check

"What if the build() method joined parts multiple times during building? How would that affect time complexity?"

Practice

1.

What is the main benefit of using a type-safe builder pattern in TypeScript?

easy

A. It ensures all required properties are set before creating the object.

B. It makes the code run faster at runtime.

C. It automatically generates UI forms.

D. It removes the need for interfaces.

Solution

1. Step 1: Understand the purpose of type-safe builder pattern

   The pattern helps build objects step-by-step while ensuring correctness.

2. Step 2: Identify the key benefit

   It uses TypeScript's type system to check that all required properties are set before final object creation.

3. Final Answer:

   It ensures all required properties are set before creating the object. -> Option A

4. Quick Check:

   Type safety = required properties checked [OK]

Hint: Remember: type-safe means catching errors before running [OK]

Common Mistakes:

• Thinking it improves runtime speed
• Confusing it with UI generation
• Assuming it removes interfaces

2.

Which of the following is the correct way to declare a generic builder class in TypeScript?

class Builder<T> {
  private data: T;
  constructor() {
    this.data = {} as T;
  }
  build(): T {
    return this.data;
  }
}

easy

A. class Builder<T> { private data: T; constructor() { this.data = undefined; } build(): T { return this.data; } }

B. class Builder { private data: any; constructor() { this.data = {}; } build(): any { return this.data; } }

C. class Builder<T> { private data: T; constructor() { this.data = {} as T; } build(): T { return this.data; } }

D. class Builder<T> { private data: T; constructor() { this.data = null; } build(): T { return this.data; } }

Solution

1. Step 1: Check generic class declaration

   class Builder<T> { private data: T; constructor() { this.data = {} as T; } build(): T { return this.data; } } correctly declares a generic class with <T> and initializes data as {} as T.

2. Step 2: Verify build method return type

   The build() method returns data typed as T, matching the generic type.

3. Final Answer:

   class Builder<T> { private data: T; constructor() { this.data = {} as T; } build(): T { return this.data; } } -> Option C

4. Quick Check:

   Generic class with typed data = class Builder<T> { private data: T; constructor() { this.data = {} as T; } build(): T { return this.data; } } [OK]

Hint: Look for generic <T> and proper initialization [OK]

Common Mistakes:

• Using any instead of generic type
• Initializing data with null or undefined
• Missing generic parameter in class

3.

Consider this TypeScript code using a type-safe builder pattern:

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

class UserBuilder {
  private user = {} as Partial<User>;
  setName(name: string) { this.user.name = name; return this; }
  setAge(age: number) { this.user.age = age; return this; }
  build(): User {
    if (!this.user.name || !this.user.age) throw new Error('Missing fields');
    return this.user as User;
  }
}

const user = new UserBuilder().setName('Alice').setAge(30).build();
console.log(user);

What will be the output?

medium

A. { name: 'Alice', age: 30 }

B. Error: Missing fields

C. undefined

D. { name: 'Alice' }

Solution

1. Step 1: Trace method calls on UserBuilder

   The builder sets name to 'Alice' and age to 30, so both required fields are set.

2. Step 2: Check build method behavior

   Since both fields exist, no error is thrown, and the object is returned as User.

3. Final Answer:

   { name: 'Alice', age: 30 } -> Option A

4. Quick Check:

   All fields set = object returned [OK]

Hint: Check if all required fields are set before build [OK]

Common Mistakes:

• Assuming error thrown even when fields set
• Expecting undefined output
• Missing age property in output

4.

Identify the error in this type-safe builder pattern code and select the fix:

interface Car {
  make: string;
  year: number;
}

class CarBuilder {
  private car = {} as Partial<Car>;
  setMake(make: string) { this.car.make = make; return this; }
  setYear(year: number) { this.car.year = year; return this; }
  build(): Car {
    if (!this.car.make || !this.car.year) throw new Error('Missing fields');
    return this.car;
  }
}

medium

A. Initialize car as Car instead of Partial<Car>

B. Change return type of build() to Partial<Car>

C. Remove the if check for missing fields

D. Cast return value as Car: return this.car as Car;

Solution

1. Step 1: Identify the type mismatch in build()

   The method returns this.car which is typed as Partial<Car>, but the return type is Car.

2. Step 2: Fix by casting to Car

   To satisfy the return type, cast this.car as Car after checking required fields.

3. Final Answer:

   Cast return value as Car: return this.car as Car; -> Option D

4. Quick Check:

   Return type must match method signature [OK]

Hint: Cast partial object to full type after validation [OK]

Common Mistakes:

• Changing return type to Partial<Car>
• Removing validation checks
• Initializing with full Car without setting fields

5.

You want to create a type-safe builder for a Product with required id and name, and optional description. Which approach best enforces setting required fields before build?

interface Product {
  id: number;
  name: string;
  description?: string;
}

// Which builder pattern enforces required fields at compile time?

hard

A. Use a single class with optional properties and runtime checks in build()

B. Use generics with flags tracking set fields and conditional types for build()

C. Use a function that returns a partial Product object without checks

D. Use inheritance to extend a base builder class without generics

Solution

1. Step 1: Understand compile-time enforcement

   Only generics with flags and conditional types can enforce required fields before build at compile time.

2. Step 2: Compare options

   Use generics with flags tracking set fields and conditional types for build() uses TypeScript generics and conditional types to track which fields are set, preventing build() call until required fields are set.

3. Final Answer:

   Use generics with flags tracking set fields and conditional types for build() -> Option B

4. Quick Check:

   Compile-time safety = generics + conditional types [OK]

Hint: Use generics and conditional types to enforce required fields [OK]

Common Mistakes:

• Relying only on runtime checks
• Using inheritance without generics
• Returning partial objects without enforcement