Nested DTO validation in NestJS - Step-by-Step Execution

Concept Flow - Nested DTO validation

Receive Request with Nested Data

↓

Parse Outer DTO

↓

Validate Outer DTO Fields

↓

Parse Nested DTO

↓

Validate Nested DTO Fields

↓

If All Valid -> Proceed

No↓

Return Validation Errors

The flow shows how NestJS receives a request, parses the outer DTO, then parses and validates nested DTOs before proceeding or returning errors.

Execution Sample

NestJS

import { IsString, ValidateNested } from 'class-validator';
import { Type } from 'class-transformer';

class AddressDto {
  @IsString()
  street: string;
}

class UserDto {
  @IsString()
  name: string;

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

Defines UserDto with a nested AddressDto, both validated for correct types.

Execution Table

Step	Action	Data Being Validated	Validation Result	Next Step
1	Receive request body	{"name":"Alice","address":{"street":"Main St"}}	N/A	Parse UserDto
2	Validate UserDto.name	"Alice"	Valid	Parse Nested AddressDto
3	Validate AddressDto.street	"Main St"	Valid	All Valid - Proceed
4	Return success	N/A	N/A	End

💡 Validation passes for all nested DTO fields, request proceeds.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
name	undefined	"Alice"	"Alice"	"Alice"
address.street	undefined	undefined	"Main St"	"Main St"

Key Moments - 2 Insights

Why do we need @ValidateNested() and @Type() decorators on nested DTOs?

Because without @ValidateNested(), the nested object won't be validated. @Type() tells class-transformer how to convert plain object to the nested DTO class. See execution_table steps 2 and 3 where nested validation happens.

What happens if nested DTO fields are missing or invalid?

Validation fails at the nested DTO step (step 3 in execution_table), and the request returns validation errors instead of proceeding.

Visual Quiz - 3 Questions

Look at the execution_table, what is validated at step 3?

A UserDto.name field

B Entire request body as a string

C AddressDto.street field

D No validation at this step

💡 Hint

Check the 'Data Being Validated' column at step 3 in execution_table.

At which step does the nested DTO validation occur?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look for 'Validate AddressDto.street' in the execution_table.

If the 'address' field was missing in the request, what would happen?

A Validation would pass because nested DTO is optional

B Validation would fail at nested DTO validation step

C Validation would fail at UserDto.name validation

D Request would be accepted without errors

💡 Hint

Refer to key_moments about missing nested DTO fields causing validation failure.

Concept Snapshot

Nested DTO Validation in NestJS:
- Use @ValidateNested() on nested DTO properties
- Use @Type(() => NestedDto) for proper transformation
- Outer DTO validates first, then nested DTOs
- Validation errors stop request processing
- Ensures deep validation of complex objects

Full Transcript

This visual execution shows how NestJS validates nested DTOs step-by-step. First, the request body is received and parsed into the outer DTO. Then, the outer DTO fields are validated. Next, the nested DTO is parsed and validated using @ValidateNested and @Type decorators. If all validations pass, the request proceeds. If any validation fails, errors are returned. This ensures that nested objects are properly checked for correctness, preventing invalid data from entering the system.