Mapped types help you create new types by changing each property of an existing type in a simple way.
Basic mapped type syntax in Typescript
type NewType = {
[Key in keyof OldType]: NewValueType;
};keyof OldType gets all keys from the old type.
The Key in keyof OldType part loops over each key.
T readonly.type Readonly<T> = {
readonly [P in keyof T]: T[P];
};T optional.type Partial<T> = {
[P in keyof T]?: T[P];
};string.type Stringify<T> = {
[P in keyof T]: string;
};This program creates a readonly version of the Person type using a mapped type. It then creates a person object with readonly properties. Trying to change a property will cause an error.
type Person = {
name: string;
age: number;
};
type ReadonlyPerson = {
readonly [K in keyof Person]: Person[K];
};
const person: ReadonlyPerson = {
name: "Alice",
age: 30
};
// person.age = 31; // Error: Cannot assign to 'age' because it is a read-only property
console.log(person.name);
console.log(person.age);Mapped types are a powerful way to transform types without repeating code.
You can add modifiers like readonly or ? inside the mapped type.
Remember, mapped types work on keys of existing types using keyof.
Mapped types create new types by looping over keys of existing types.
You can change property modifiers or types easily with mapped types.
This helps keep your code DRY and consistent.
Practice
Solution
Step 1: Understand mapped types concept
Mapped types create new types by iterating over keys of an existing type, transforming them.Step 2: Differentiate from runtime behavior
Mapped types work at compile time for types, not runtime functions or imports.Final Answer:
Creates a new type by looping over keys of an existing type -> Option DQuick Check:
Mapped type = new type from keys [OK]
- Confusing mapped types with runtime loops
- Thinking mapped types define classes
- Mixing mapped types with imports
Solution
Step 1: Identify mapped type syntax
Mapped types use square brackets with 'in' keyword: {[K in keyof T]: T[K]}Step 2: Check each option
type NewType<T> = { [K in keyof T]: T[K] } matches correct syntax; B uses arrow function incorrectly; C lacks 'in' keyword; D uses string index, not keys of T.Final Answer:
type NewType<T> = { [K in keyof T]: T[K] } -> Option CQuick Check:
Mapped type syntax = {[K in keyof T]: T[K]} [OK]
- Using arrow functions instead of mapped syntax
- Missing 'in' keyword inside brackets
- Using string index instead of keyof T
type Flags = { a: boolean; b: boolean; }, what is the type of type ReadonlyFlags = { readonly [K in keyof Flags]: Flags[K] }?Solution
Step 1: Understand the mapped type with readonly modifier
The mapped type adds 'readonly' before each property key, making all properties readonly.Step 2: Compare with original type
Original Flags has mutable properties; ReadonlyFlags has same keys but readonly modifier added.Final Answer:
{ readonly a: boolean; readonly b: boolean; } -> Option BQuick Check:
Readonly mapped type adds readonly modifier [OK]
- Ignoring readonly modifier effect
- Confusing optional properties with readonly
- Assuming type changes keys or values
type PartialType<T> = { [K of keyof T]?: T[K] }Solution
Step 1: Check mapped type syntax
The correct keyword inside mapped types is 'in', not 'of'.Step 2: Validate other parts
Optional modifier '?' is valid; semicolon is optional; 'keyof T' is correct syntax.Final Answer:
Using 'of' instead of 'in' in the mapped type syntax -> Option AQuick Check:
Mapped types use 'in' keyword [OK]
- Confusing 'in' with 'of' keyword
- Thinking '?' is invalid in mapped types
- Assuming semicolon is mandatory
Solution
Step 1: Combine readonly and optional modifiers correctly
In mapped types, 'readonly' goes before the key, and '?' after the key to make properties optional and readonly.Step 2: Analyze each option
type OptionalReadonly<T> = { readonly [K in keyof T]?: T[K] } correctly places 'readonly' before [K] and '?' after [K]. Options B, C, D misuse placement of modifiers.Final Answer:
type OptionalReadonly<T> = { readonly [K in keyof T]?: T[K] } -> Option AQuick Check:
Readonly + optional = readonly [K in keyof T]? [OK]
- Placing '?' before 'readonly'
- Putting 'readonly' after the key
- Misplacing optional modifier on type instead of key
Ready to prove it?
Pass the test and this pattern moves unknown
