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.

Practice

1. What is the main purpose of using ValidationPipe in a NestJS application?

easy

A. To serve static files like images and CSS

B. To handle database connections automatically

C. To check and clean incoming data to ensure it is safe and correct

D. To manage user authentication and authorization

Solution

1. Step 1: Understand ValidationPipe role

   ValidationPipe is designed to validate and sanitize incoming data in NestJS, ensuring the data meets expected rules.

2. Step 2: Compare with other options

   Other options like database handling, authentication, or serving static files are unrelated to ValidationPipe's purpose.

3. Final Answer:

   To check and clean incoming data to ensure it is safe and correct -> Option C

4. Quick Check:

   ValidationPipe purpose = data validation and cleaning [OK]

Hint: ValidationPipe is all about checking incoming data [OK]

Common Mistakes:

• Confusing ValidationPipe with authentication features
• Thinking ValidationPipe manages database connections
• Assuming ValidationPipe serves static files

2. Which is the correct way to apply ValidationPipe globally in a NestJS app inside main.ts?

easy

A. app.useGlobalPipes(new ValidationPipe())

B. app.usePipes(new ValidationPipe())

C. app.setGlobalPipes(new ValidationPipe())

D. app.applyGlobalPipes(new ValidationPipe())

Solution

1. Step 1: Recall NestJS global pipe method

   The official method to set global pipes is app.useGlobalPipes().

2. Step 2: Check other options

   Methods like usePipes, setGlobalPipes, or applyGlobalPipes do not exist or are incorrect.

3. Final Answer:

   app.useGlobalPipes(new ValidationPipe()) -> Option A

4. Quick Check:

   Global pipe setup = useGlobalPipes() [OK]

Hint: Global pipes use app.useGlobalPipes() [OK]

Common Mistakes:

• Using non-existent methods like setGlobalPipes
• Confusing useGlobalPipes with usePipes
• Missing the 'new' keyword before ValidationPipe

3. Given this main.ts snippet, what will happen when a request sends extra properties not defined in the DTO?

app.useGlobalPipes(new ValidationPipe({ whitelist: true }));

medium

A. The request will fail with a validation error

B. Extra properties will be removed from the incoming data

C. Extra properties will be kept without changes

D. The app will crash due to unknown properties

Solution

1. Step 1: Understand whitelist option in ValidationPipe

   Setting whitelist: true removes any properties not defined in the DTO from the incoming data.

2. Step 2: Check behavior on extra properties

   With whitelist true, extra properties are stripped, not causing errors or crashes.

3. Final Answer:

   Extra properties will be removed from the incoming data -> Option B

4. Quick Check:

   whitelist true = remove extra props [OK]

Hint: whitelist true strips unknown properties [OK]

Common Mistakes:

• Thinking whitelist causes validation errors on extra props
• Assuming extra props are kept unchanged
• Believing app crashes on extra properties

4. What is wrong with this main.ts code snippet for setting up ValidationPipe globally?

app.useGlobalPipes(ValidationPipe({ transform: true }));

medium

A. Missing 'new' keyword before ValidationPipe

B. The 'transform' option is invalid

C. useGlobalPipes should be called inside a controller

D. ValidationPipe cannot be used globally

Solution

1. Step 1: Check ValidationPipe instantiation

   ValidationPipe is a class and must be instantiated with the new keyword.

2. Step 2: Validate other parts

   The transform option is valid, and useGlobalPipes is correctly used in main.ts.

3. Final Answer:

   Missing 'new' keyword before ValidationPipe -> Option A

4. Quick Check:

   Instantiate ValidationPipe with new [OK]

Hint: Always use 'new' with ValidationPipe class [OK]

Common Mistakes:

• Omitting 'new' keyword when creating ValidationPipe
• Thinking transform option is invalid
• Trying to set global pipes inside controllers

5. You want to automatically convert incoming JSON strings to their expected types in your DTOs. Which ValidationPipe option should you enable globally to achieve this?

hard

A. forbidNonWhitelisted: true

B. whitelist: true

C. disableErrorMessages: true

D. transform: true

Solution

1. Step 1: Understand transform option

   Setting transform: true tells ValidationPipe to convert incoming payloads to the types defined in DTO classes automatically.

2. Step 2: Check other options

   whitelist removes extra properties, forbidNonWhitelisted throws errors on extra props, and disableErrorMessages hides validation errors; none convert types.

3. Final Answer:

   transform: true -> Option D

4. Quick Check:

   transform true = auto type conversion [OK]

Hint: Use transform true to convert types automatically [OK]

Common Mistakes:

• Confusing whitelist with type conversion
• Thinking forbidNonWhitelisted converts types
• Believing disableErrorMessages affects data types