Nested DTO validation in NestJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a DTO in NestJS and why do we use it?

A DTO (Data Transfer Object) is a simple object that defines how data is sent over the network. We use it to validate and type-check incoming data to keep our app safe and organized.

intermediate

How do you enable validation for nested objects inside a DTO in NestJS?

Use the @ValidateNested() decorator on the nested property and add @Type(() => NestedDtoClass) from 'class-transformer' to tell NestJS how to transform and validate the nested object.

intermediate

What decorators are commonly used to validate nested DTO properties in NestJS?

Common decorators are @ValidateNested() to trigger nested validation and @Type(() => ClassName) to transform plain objects into class instances for validation.

intermediate

Why do we need to use @Type(() => ClassName) when validating nested DTOs?

Because validation works on class instances, @Type() converts plain JSON objects into class instances so the validation decorators inside the nested DTO can run properly.

beginner

What happens if you forget to use @ValidateNested() on a nested DTO property?

The nested object will not be validated, so invalid or missing data inside it might pass through without errors, causing potential bugs or security issues.

Which decorator is essential to validate nested DTO properties in NestJS?

A @IsNotEmpty()

B @ValidateNested()

C @IsString()

D @IsNumber()

@ValidateNested() tells NestJS to validate the nested object using its own validation rules.

What is the role of @Type(() => ClassName) in nested DTO validation?

A Marks a property as optional

B Checks if a value is a string

C Transforms plain objects into class instances for validation

D Sets a default value

@Type() from class-transformer converts plain JSON into class instances so validation decorators work.

If you have a nested DTO property without @ValidateNested(), what happens?

A Nested validation is skipped

B Validation runs normally

C App crashes

D Property is ignored completely

Without @ValidateNested(), the nested object's validation rules are not applied.

Which package provides the @ValidateNested() decorator used in NestJS DTO validation?

A class-transformer

B rxjs

C nestjs/common

D class-validator

@ValidateNested() comes from class-validator to enable nested validation.

What must you do to validate an array of nested DTOs?

A Use @ValidateNested({ each: true }) and @Type(() => NestedDto)

B Use only @IsArray()

C Use @IsString() on the array

D No special decorators needed

For arrays, @ValidateNested({ each: true }) validates each item, and @Type() transforms each item.

Explain how to set up nested DTO validation in NestJS step-by-step.

Think about how NestJS knows to check inside nested objects.

Why is it important to use both @ValidateNested() and @Type() together for nested DTOs?

One decorator triggers validation, the other prepares the data for it.

Practice

1. What is the main purpose of using @ValidateNested() in a NestJS DTO?

easy

A. To define default values for nested properties

B. To convert nested objects to plain JavaScript objects

C. To skip validation of nested objects

D. To validate properties of nested objects inside the DTO automatically

Solution

1. Step 1: Understand the role of @ValidateNested()

   This decorator tells NestJS to validate nested objects inside a DTO, not just the top-level properties.

2. Step 2: Compare with other options

   @Type() handles transformation, not validation. Skipping validation or setting defaults is unrelated to @ValidateNested().

3. Final Answer:

   To validate properties of nested objects inside the DTO automatically -> Option D

4. Quick Check:

   @ValidateNested() = validate nested objects [OK]

Hint: Remember: @ValidateNested() triggers nested object validation [OK]

Common Mistakes:

• Confusing @ValidateNested() with @Type()
• Thinking it skips validation
• Assuming it sets default values

2. Which of the following is the correct way to apply nested validation in a DTO property?

easy

A. Use both @ValidateNested() and @Type(() => NestedDto)

B. Use @ValidateNested() only

C. Use @Type(() => NestedDto) only

D. Use @IsString() on the nested property

Solution

1. Step 1: Identify decorators needed for nested validation

   @ValidateNested() triggers validation of nested objects, but @Type() is needed to transform plain objects into class instances.

2. Step 2: Understand why both are required

   Without @Type(), validation won't work properly because the nested object won't be recognized as the correct class type.

3. Final Answer:

   Use both @ValidateNested() and @Type(() => NestedDto) -> Option A

4. Quick Check:

   Nested validation = @ValidateNested() + @Type() [OK]

Hint: Always pair @ValidateNested() with @Type() for nested DTOs [OK]

Common Mistakes:

• Using only one decorator and expecting full validation
• Applying @IsString() on an object property
• Forgetting to import Type from class-transformer

3. Given the following DTOs, what will happen if address.zipCode is missing when validating UserDto?

class AddressDto {
  @IsString()
  street: string;

  @IsString()
  zipCode: string;
}

class UserDto {
  @IsString()
  name: string;

  @ValidateNested()
  @Type(() => AddressDto)
  address: AddressDto;
}

medium

A. Validation will fail because zipCode is missing

B. Validation will pass because zipCode is optional

C. Validation will fail because name is missing

D. Validation will pass but address will be undefined

Solution

1. Step 1: Check required properties in AddressDto

   Both street and zipCode are decorated with @IsString(), so they are required and must be strings.

2. Step 2: Understand nested validation in UserDto

   @ValidateNested() with @Type() ensures address is validated as AddressDto, so missing zipCode causes validation to fail.

3. Final Answer:

   Validation will fail because zipCode is missing -> Option A

4. Quick Check:

   Missing required nested property = validation fails [OK]

Hint: Missing required nested fields cause validation failure [OK]

Common Mistakes:

• Assuming missing nested fields are allowed by default
• Ignoring the effect of @ValidateNested()
• Confusing missing nested fields with missing top-level fields

4. Consider this DTO code snippet:

class ProfileDto {
  @IsString()
  bio: string;
}

class UserDto {
  @IsString()
  username: string;

  @ValidateNested()
  profile: ProfileDto;
}

Why will validation NOT work correctly for the nested profile property?

medium

A. Because @ValidateNested() should be on ProfileDto class

B. Because @IsString() is missing on profile

C. Because @Type(() => ProfileDto) decorator is missing on profile

D. Because bio property is missing @ValidateNested()

Solution

1. Step 1: Identify missing decorator for nested validation

   For nested validation to work, @Type(() => ProfileDto) must be added to the nested property to transform plain objects into class instances.

2. Step 2: Understand why other options are incorrect

   @IsString() is for string properties, not objects. @ValidateNested() belongs on the nested property, not the nested class. bio is a string, no nested validation needed.

3. Final Answer:

   Because @Type(() => ProfileDto) decorator is missing on profile -> Option C

4. Quick Check:

   Missing @Type() breaks nested validation [OK]

Hint: Always add @Type() with @ValidateNested() for nested DTOs [OK]

Common Mistakes:

• Forgetting @Type() on nested properties
• Misplacing @ValidateNested() on nested class
• Confusing property decorators with class decorators

5. You have a CompanyDto with a nested array of EmployeeDto objects. Which is the correct way to validate this nested array properly?

class EmployeeDto {
  @IsString()
  name: string;

  @IsInt()
  age: number;
}

class CompanyDto {
  @IsString()
  companyName: string;

  @ValidateNested({ each: true })
  @Type(() => EmployeeDto)
  employees: EmployeeDto[];
}

hard

A. You must remove { each: true } from @ValidateNested() for arrays

B. This setup correctly validates each employee in the employees array

C. You should use @IsArray() instead of @ValidateNested() for employees

D. You need to add @IsOptional() to employees to validate nested arrays

Solution

1. Step 1: Understand nested array validation

   For arrays of nested objects, @ValidateNested({ each: true }) tells the validator to check each item in the array.

2. Step 2: Confirm use of @Type() for transformation

   @Type(() => EmployeeDto) converts plain objects to EmployeeDto instances, enabling validation on each employee.

3. Final Answer:

   This setup correctly validates each employee in the employees array -> Option B

4. Quick Check:

   Nested arrays need @ValidateNested({ each: true }) + @Type() [OK]

Hint: Use { each: true } with @ValidateNested() for nested arrays [OK]

Common Mistakes:

• Omitting { each: true } for arrays
• Using @IsArray() alone without nested validation
• Forgetting @Type() for nested array items