Why pipes transform and validate input in NestJS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Pipes in NestJS

What is the primary reason NestJS pipes transform and validate input data?

A To delay the processing of requests until the server is less busy

B To encrypt input data for security before processing

C To automatically generate database queries from input data

D To ensure input data meets expected format and types before reaching route handlers

💡 Hint

Think about how pipes help keep your application safe and predictable.

Pipes in NestJS are used to transform and validate input data so that the data passed to route handlers is clean and correctly typed. This prevents errors and security issues.

❓ component_behavior

intermediate

Effect of Validation Pipe on Controller Input

Given a NestJS controller using a ValidationPipe, what happens if the input data does not match the DTO validation rules?

NestJS

import { Controller, Post, Body, UsePipes, ValidationPipe } from '@nestjs/common';
import { IsInt, Min } from 'class-validator';

class AgeDto {
  @IsInt()
  @Min(0)
  age: number;
}

@Controller('users')
export class UserController {
  @Post('age')
  @UsePipes(new ValidationPipe())
  setAge(@Body() ageDto: AgeDto) {
    return `Age set to ${ageDto.age}`;
  }
}

A The request is rejected with a 400 Bad Request error and validation details

B The input is accepted but logged as a warning

C The controller sets age to zero by default and returns success

D The server crashes due to unhandled validation errors

💡 Hint

ValidationPipe stops invalid data from reaching the controller.

ValidationPipe automatically checks input against DTO rules. If validation fails, it throws an exception that results in a 400 error response with details.

📝 Syntax

advanced

Correct Use of Transform in a Custom Pipe

Which option correctly implements a NestJS pipe that transforms a string input to uppercase before passing it to the handler?

NestJS

import { PipeTransform, Injectable, ArgumentMetadata } from '@nestjs/common';

@Injectable()
export class UppercasePipe implements PipeTransform {
  transform(value: any, metadata: ArgumentMetadata) {
    // Transform logic here
  }
}

A return value.uppercase();

B return value.toUpperCase();

C return value.toUpper();

D return value.toUpperCase

💡 Hint

Check the correct JavaScript string method for uppercase conversion.

The correct method to convert a string to uppercase in JavaScript is toUpperCase(). Other options are invalid or undefined methods.

🔧 Debug

advanced

Identifying Pipe Validation Error Cause

A NestJS app uses a ValidationPipe globally. A POST request with body {"age": "twenty"} is sent to a route expecting a DTO with @IsInt() age property. What error will occur and why?

A 400 Bad Request because 'twenty' is not an integer

B 500 Internal Server Error due to type mismatch

C Request succeeds but age is set to 0

D No error, input is accepted as string

💡 Hint

ValidationPipe enforces type and format rules strictly.

The ValidationPipe checks that 'age' is an integer. The string 'twenty' fails this check, causing a 400 error response.

❓ state_output

expert

Output of a Pipe Transforming and Validating Input

Consider this NestJS pipe that transforms input to a number and validates it is positive. What is the output when input is '-5'?

NestJS

import { PipeTransform, Injectable, BadRequestException } from '@nestjs/common';

@Injectable()
export class PositiveNumberPipe implements PipeTransform {
  transform(value: any) {
    const val = Number(value);
    if (isNaN(val) || val <= 0) {
      throw new BadRequestException('Value must be a positive number');
    }
    return val;
  }
}

// Usage in controller:
// @UsePipes(new PositiveNumberPipe())
// someMethod(@Body('amount') amount: number) { return amount; }

A Returns string '-5' without change

B Returns -5 as a number

C Throws BadRequestException with message 'Value must be a positive number'

D Returns 0 because negative values are reset

💡 Hint

Check the condition that triggers the exception in the transform method.

The pipe converts input to number and checks if it is positive. Since -5 is not positive, it throws a BadRequestException.