Partial type in Typescript - Time & Space Complexity

Time Complexity: Partial type

O(n)

Understanding Time Complexity

Let's explore how the time it takes to create a partial type grows as the size of the original type grows.

We want to know how the work changes when we make some or all properties optional.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    type User = {
      id: number;
      name: string;
      email: string;
      age: number;
    };

    type PartialUser = Partial;
    

This code creates a new type where all properties of User become optional.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Iterating over each property of the original type.
• How many times: Once for each property in the type.

How Execution Grows With Input

As the number of properties increases, the work to make them optional grows linearly.

Input Size (number of properties)	Approx. Operations
10	10 operations
100	100 operations
1000	1000 operations

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

Final Time Complexity

Time Complexity: O(n)

This means the time to create a partial type grows in a straight line with the number of properties.

Common Mistake

[X] Wrong: "Making a partial type is instant and does not depend on the number of properties."

[OK] Correct: Each property must be processed to become optional, so more properties mean more work.

Interview Connect

Understanding how type transformations scale helps you reason about code maintainability and compiler work behind the scenes.

Self-Check

"What if we used a nested type with properties that are themselves objects? How would the time complexity change?"

Practice

1.

What does the Partial utility type do in TypeScript?

easy

A. Changes all properties to readonly

B. Makes all properties of a type required

C. Removes all properties from a type

D. Makes all properties of a type optional

Solution

1. Step 1: Understand the purpose of Partial

   The Partial type is designed to take an existing type and make all its properties optional.

2. Step 2: Compare with other utility types

   Unlike Required which makes all properties mandatory, Partial does the opposite by making them optional.

3. Final Answer:

   Makes all properties of a type optional -> Option D

4. Quick Check:

   Partial = optional properties [OK]

Hint: Partial makes properties optional, not required or readonly [OK]

Common Mistakes:

• Confusing Partial with Required
• Thinking Partial removes properties
• Assuming Partial makes properties readonly

2.

Which of the following is the correct syntax to create a partial type of User?

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

easy

A. type PartialUser = Partial<User>;

B. type PartialUser = User.Partial;

C. type PartialUser = Partial<User> = {};

D. type PartialUser = Partial<User> {};

Solution

1. Step 1: Recall correct Partial syntax

   The correct way to create a partial type is using Partial<Type> syntax.

2. Step 2: Check each option

   type PartialUser = Partial<User>; uses correct syntax. Options A, B, and D have invalid or incorrect TypeScript syntax.

3. Final Answer:

   type PartialUser = Partial<User>; -> Option A

4. Quick Check:

   Partial syntax = Partial<Type> [OK]

Hint: Use Partial<Type> to create partial types [OK]

Common Mistakes:

• Using dot notation instead of generic syntax
• Adding extra equals or braces incorrectly
• Confusing Partial with object literals

3.

What is the output of this TypeScript code?

interface Product { id: number; name: string; price: number; }
const updateProduct: Partial<Product> = { price: 99 };
console.log(updateProduct);

medium

A. { id: undefined, name: undefined, price: 99 }

B. { price: 99 }

C. Error: Missing properties id and name

D. {}

Solution

1. Step 1: Understand Partial effect on properties

   Partial makes all properties optional, so you can provide only some properties.

2. Step 2: Check the object assigned

   The object has only price: 99. This is valid and prints exactly that.

3. Final Answer:

   { price: 99 } -> Option B

4. Quick Check:

   Partial allows partial objects [OK]

Hint: Partial lets you omit properties safely [OK]

Common Mistakes:

• Expecting all properties to appear with undefined
• Thinking missing properties cause errors
• Assuming Partial creates empty objects

4.

Identify the error in this code snippet:

interface Settings { theme: string; fontSize: number; }
const newSettings: Partial<Settings> = { theme: 'dark' };
newSettings.fontSize.toFixed(2);

medium

A. Error: toFixed is not a function

B. No error, code runs fine

C. Error: fontSize might be undefined

D. Error: theme property missing

Solution

1. Step 1: Analyze Partial type effect

   Partial makes all properties optional, so fontSize may be undefined.

2. Step 2: Check method call on possibly undefined

   Calling toFixed on possibly undefined fontSize causes a runtime error.

3. Final Answer:

   Error: fontSize might be undefined -> Option C

4. Quick Check:

   Partial properties can be undefined [OK]

Hint: Check for undefined before using Partial properties [OK]

Common Mistakes:

• Ignoring optional property undefined possibility
• Assuming all properties exist
• Confusing method errors with type errors

5.

You have this interface and partial update function:

interface Profile { username: string; email: string; age: number; }
function updateProfile(profile: Profile, updates: Partial<Profile>): Profile {
  return { ...profile, ...updates };
}

What is the result of calling updateProfile({ username: 'alice', email: '[e-mail]', age: 30 }, { email: '[e-mail]' })?

hard

A. { username: 'alice', email: '[e-mail]', age: 30 }

B. { username: 'alice', email: '[e-mail]', age: 30 }

C. Error: Cannot spread Partial type

D. { email: '[e-mail]' }

Solution

1. Step 1: Understand spread with Partial

   The function merges the original profile with updates, overwriting provided fields.

2. Step 2: Apply the update

   The email field is replaced with the new value, others remain unchanged.

3. Final Answer:

   { username: 'alice', email: '[e-mail]', age: 30 } -> Option A

4. Quick Check:

   Spread merges updates over original [OK]

Hint: Spread merges partial updates over full object [OK]

Common Mistakes:

• Thinking Partial cannot be spread
• Expecting original email to remain
• Returning only updates without original fields