Required type in Typescript - Time & Space Complexity

Time Complexity: Required type

O(n)

Understanding Time Complexity

Let's see how the time it takes to run code changes when we use the Required type in TypeScript.

We want to know how the program's work grows as the input gets bigger.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

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

function makeRequired(obj: Person): Required<Person> {
  return {
    name: obj.name!,
    age: obj.age!,
    city: obj.city!
  };
}
    

This code takes an object with optional properties and returns a new object where all properties are required.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Accessing each property once to assign it to the new object.
• How many times: Exactly once per property (3 properties here).

How Execution Grows With Input

Since the number of properties is fixed, the work per object stays the same no matter how many objects we process.

Input Size (n)	Approx. Operations
10 objects	10 x 3 = 30 property accesses
100 objects	100 x 3 = 300 property accesses
1000 objects	1000 x 3 = 3000 property accesses

Pattern observation: The work grows linearly with the number of objects processed.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete grows directly in proportion to how many objects we convert.

Common Mistake

[X] Wrong: "Using Required type makes the code slower because it forces extra checks at runtime."

[OK] Correct: Required is a compile-time tool that changes types but does not add runtime loops or checks; the runtime cost depends on how many objects you process, not on the type itself.

Interview Connect

Understanding how type utilities like Required affect your code helps you write clear and efficient programs, a skill that shows you think about both correctness and performance.

Self-Check

"What if the object had 100 properties instead of 3? How would the time complexity change?"

Practice

1. What does the Required utility type do in TypeScript?

easy

A. Makes all properties of a type optional

B. Makes all properties of a type mandatory

C. Removes all properties from a type

D. Allows properties to be undefined

Solution

1. Step 1: Understand the purpose of Required

   The Required utility type transforms all optional properties of a type into required ones.

2. Step 2: Compare options with definition

   Only Makes all properties of a type mandatory correctly states that Required makes all properties mandatory.

3. Final Answer:

   Makes all properties of a type mandatory -> Option B

4. Quick Check:

   Required = all mandatory [OK]

Hint: Remember: Required means no optional properties allowed [OK]

Common Mistakes:

• Confusing Required with Partial (which makes properties optional)
• Thinking Required removes properties
• Assuming Required allows undefined values

2. Which of the following is the correct syntax to make all properties of interface User required using Required?

easy

A. type CompleteUser = Required<User>;

B. type CompleteUser = Partial<User>;

C. type CompleteUser = Optional<User>;

D. type CompleteUser = Readonly<User>;

Solution

1. Step 1: Recall the syntax of Required

   The correct syntax to apply Required is Required<TypeName>.

2. Step 2: Match options with syntax

   type CompleteUser = Required<User>; uses Required<User> correctly. Others use different utility types or incorrect names.

3. Final Answer:

   type CompleteUser = Required<User>; -> Option A

4. Quick Check:

   Use Required<Type> for all mandatory props [OK]

Hint: Use Required<Type> exactly to enforce all properties [OK]

Common Mistakes:

• Using Partial instead of Required
• Typing Optional which doesn't exist in TypeScript
• Confusing Readonly with Required

3. Given the interface and type below, what is the type of user2?

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

const user2: Required<User> = {
  name: "Alice",
  age: 30
};

medium

A. An object where name and age are required

B. An object where name and age are optional

C. An object where only name is required

D. An object where age is optional

Solution

1. Step 1: Analyze the interface User

   Both name and age are optional properties in User.

2. Step 2: Understand Required<User>

   The Required utility makes all optional properties required, so name and age must be present.

3. Final Answer:

   An object where name and age are required -> Option A

4. Quick Check:

   Required<User> = all required props [OK]

Hint: Required makes all optional props mandatory [OK]

Common Mistakes:

• Thinking optional props stay optional
• Assuming only some props become required
• Confusing Required with Partial

4. What is the error in this code snippet?

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

const product: Required<Product> = {
  id: 101
};

medium

A. Cannot assign object to interface Product

B. Type 'number' is not assignable to 'string'

C. No error, code is correct

D. Missing property 'name' in object

Solution

1. Step 1: Check properties in Required<Product>

   Both id and name are required because of Required.

2. Step 2: Compare object properties with interface

   The object only has id, missing name, causing a TypeScript error.

3. Final Answer:

   Missing property 'name' in object -> Option D

4. Quick Check:

   Required means all props must be present [OK]

Hint: Check all required props are present in object [OK]

Common Mistakes:

• Ignoring missing required properties
• Thinking optional props remain optional
• Assuming partial object assignment is allowed

5. You have a type with some optional properties:

type Config = {
  host?: string;
  port?: number;
  secure?: boolean;
};

You want to create a new type FullConfig where all properties are required, but also want to add a new property timeout which is required. Which is the correct way to do this?

hard

A. type FullConfig = Partial<Config> & { timeout?: number };

B. type FullConfig = Required<Config> & { timeout?: number };

C. type FullConfig = Required<Config> & { timeout: number };

D. type FullConfig = Config & { timeout: number };

Solution

1. Step 1: Make all Config properties required

   Use Required<Config> to make host, port, and secure mandatory.

2. Step 2: Add new required property timeout

   Use intersection & with { timeout: number } to add a required timeout property.

3. Final Answer:

   type FullConfig = Required<Config> & { timeout: number }; -> Option C

4. Quick Check:

   Required + intersection adds required props [OK]

Hint: Combine Required<Type> & { newProp: type } for extra required props [OK]

Common Mistakes:

• Using Partial instead of Required
• Making new property optional when it should be required
• Not combining types correctly