ValidationPipe setup in NestJS - Step-by-Step Execution

Concept Flow - ValidationPipe setup

Create ValidationPipe instance

↓

Apply pipe globally or to route

↓

Incoming request data

↓

ValidationPipe runs validation

↓

Pass data to

This flow shows how ValidationPipe is created, applied, and then validates incoming data, allowing valid data through or rejecting invalid data.

Execution Sample

NestJS

import { ValidationPipe } from '@nestjs/common';

app.useGlobalPipes(new ValidationPipe());

@Post()
create(@Body() dto: CreateDto) {
  return this.service.create(dto);
}

This code sets up ValidationPipe globally to validate incoming request bodies against DTO rules.

Execution Table

Step	Action	Input Data	Validation Result	Outcome
1	Create ValidationPipe instance	N/A	N/A	ValidationPipe ready
2	Apply ValidationPipe globally	N/A	N/A	Pipe intercepts all requests
3	Receive POST request with body	{ name: 'John', age: 30 }	Valid	Data passed to controller
4	Controller calls service.create(dto)	{ name: 'John', age: 30 }	N/A	Service processes data
5	Receive POST request with body	{ name: '', age: -5 }	Invalid	Validation error thrown
6	Send error response	{ name: '', age: -5 }	N/A	Client receives validation errors

💡 Execution stops when request is either passed to controller or rejected by validation error.

Variable Tracker

Variable	Start	After Step 3	After Step 5	Final
ValidationPipe	Not created	Instance created	Instance created	Instance active
Request Body	N/A	{ name: 'John', age: 30 }	{ name: '', age: -5 }	Depends on request
Validation Result	N/A	Valid	Invalid	N/A

Key Moments - 2 Insights

Why does the request get rejected when ValidationPipe is applied?

Because ValidationPipe checks the data against DTO rules and if data is invalid (see step 5 in execution_table), it throws an error instead of passing data to the controller.

How does applying ValidationPipe globally affect requests?

Applying it globally means every incoming request body is automatically validated before reaching any controller, as shown in step 2 and 3.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 5?

A Data is valid and passed to controller

B Validation error is thrown due to invalid data

C ValidationPipe instance is created

D Service processes the data

💡 Hint

Check the 'Validation Result' and 'Outcome' columns at step 5 in execution_table

According to variable_tracker, what is the ValidationPipe state after step 3?

A Instance created

B Not created

C Instance destroyed

D Inactive

💡 Hint

Look at the ValidationPipe row and After Step 3 column in variable_tracker

If ValidationPipe was not applied globally, what would change in the execution_table?

A Validation would still happen for all requests

B ValidationPipe instance would not be created

C No validation would occur unless pipe applied to specific routes

D Service would reject all data

💡 Hint

Consider step 2 where pipe is applied globally and its effect on validation

Concept Snapshot

ValidationPipe setup in NestJS:
- Create ValidationPipe instance
- Apply globally with app.useGlobalPipes(new ValidationPipe())
- Incoming request data is validated automatically
- Valid data passes to controller
- Invalid data triggers error response
- Ensures data integrity before business logic

Full Transcript

This visual execution shows how ValidationPipe is set up in NestJS. First, a ValidationPipe instance is created. Then it is applied globally so it intercepts all incoming requests. When a POST request arrives, the pipe validates the request body against defined DTO rules. If the data is valid, it passes to the controller and service for processing. If invalid, the pipe throws a validation error and the client receives an error response. Variables like ValidationPipe instance and request body change state as the request flows through the system. Key moments include understanding why invalid data is rejected and how global application affects all routes. The quiz tests understanding of these steps and states.