ValidationPipe in depth in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to apply ValidationPipe globally in a NestJS app.

NestJS

app.useGlobalPipes(new [1]());

Drag options to blanks, or click blank then click option'

AValidationPipe

BParseIntPipe

CAuthGuard

DLogger

Attempts:

3 left

💡 Hint

Common Mistakes

Using a pipe that does not validate data like ParseIntPipe.

Forgetting to create a new instance with parentheses.

The ValidationPipe is used to validate incoming requests globally in NestJS.

2fill in blank

medium

Complete the code to enable automatic transformation of input data types in ValidationPipe.

NestJS

app.useGlobalPipes(new ValidationPipe({ [1]: true }));

Drag options to blanks, or click blank then click option'

Atransform

Bwhitelist

CforbidNonWhitelisted

DskipMissingProperties

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'whitelist' with 'transform'.

Not enabling transform causes input to remain strings.

The transform option converts input data to the expected types automatically.

3fill in blank

hard

Fix the error in the code to forbid properties not in the DTO during validation.

NestJS

app.useGlobalPipes(new ValidationPipe({ [1]: true }));

Drag options to blanks, or click blank then click option'

AskipMissingProperties

BdisableErrorMessages

Ctransform

DforbidNonWhitelisted

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'whitelist' instead of 'forbidNonWhitelisted'.

Not enabling this option allows extra properties silently.

The forbidNonWhitelisted option throws an error if extra properties are sent.

4fill in blank

hard

Fill both blanks to create a ValidationPipe that strips unknown properties and skips missing ones.

NestJS

new ValidationPipe({ [1]: true, [2]: true })

Drag options to blanks, or click blank then click option'

Awhitelist

BskipMissingProperties

CforbidNonWhitelisted

Dtransform

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'forbidNonWhitelisted' with 'whitelist'.

Not using 'skipMissingProperties' when optional fields are missing.

whitelist removes unknown properties, and skipMissingProperties allows missing optional fields.

5fill in blank

hard

Fill all three blanks to create a ValidationPipe with transformation, whitelist, and forbidding unknown properties.

NestJS

new ValidationPipe({ [1]: true, [2]: true, [3]: true })

Drag options to blanks, or click blank then click option'

AskipMissingProperties

Bwhitelist

CforbidNonWhitelisted

Dtransform

Attempts:

3 left

💡 Hint

Common Mistakes

Missing one of the three options causes unexpected behavior.

Confusing 'skipMissingProperties' with 'forbidNonWhitelisted'.

This pipe transforms input types, removes unknown properties, and forbids extra properties.

Practice

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

easy

A. To check and clean incoming data before it is used

B. To handle database connections automatically

C. To manage user authentication and sessions

D. To serve static files like images and CSS

Solution

1. Step 1: Understand ValidationPipe role

   ValidationPipe is designed to validate and sanitize incoming request data to ensure it meets expected rules.

2. Step 2: Compare with other options

   Options B, C, and D relate to other parts of NestJS or web apps, not data validation.

3. Final Answer:

   To check and clean incoming data before it is used -> Option A

4. Quick Check:

   ValidationPipe purpose = data validation [OK]

Hint: ValidationPipe = data check and clean before use [OK]

Common Mistakes:

• Confusing ValidationPipe with authentication or database handling
• Thinking ValidationPipe serves static files
• Assuming ValidationPipe manages sessions

2. Which of the following is the correct way to enable automatic transformation of input data types using ValidationPipe in NestJS?

easy

A. new ValidationPipe({ forbidNonWhitelisted: true })

B. new ValidationPipe({ whitelist: true })

C. new ValidationPipe({ transform: true })

D. new ValidationPipe({ skipMissingProperties: true })

Solution

1. Step 1: Identify transform option

   The transform: true option enables automatic conversion of input data types to expected types.

2. Step 2: Understand other options

   whitelist removes unwanted properties, forbidNonWhitelisted throws error on extra props, skipMissingProperties skips validation for missing props.

3. Final Answer:

   new ValidationPipe({ transform: true }) -> Option C

4. Quick Check:

   transform option enables type conversion [OK]

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

Common Mistakes:

• Confusing whitelist with transform
• Using forbidNonWhitelisted to transform data
• Thinking skipMissingProperties enables transformation

3. Given this DTO and ValidationPipe setup, what will be the output when sending { "age": "25" } in the request body?

class UserDto {
  @IsInt()
  age: number;
}

// In controller
@Post()
create(@Body(new ValidationPipe({ transform: true })) user: UserDto) {
  return typeof user.age;
}

medium

A. "string"

B. "undefined"

C. Validation error thrown

D. "number"

Solution

1. Step 1: Check ValidationPipe transform option

   Transform is true, so input string "25" will be converted to number 25.

2. Step 2: Determine returned type

   Since age is transformed to number, typeof user.age returns "number".

3. Final Answer:

   "number" -> Option D

4. Quick Check:

   transform converts string to number, so typeof = "number" [OK]

Hint: transform: true converts strings to numbers automatically [OK]

Common Mistakes:

• Assuming input stays string without transform
• Expecting validation error for string number
• Thinking age is undefined without explicit conversion

4. Identify the error in this ValidationPipe usage that causes unexpected behavior:

@Post()
create(@Body(new ValidationPipe({ whitelist: true })) user: UserDto) {
  return user;
}

// UserDto has properties: name (string), age (number)

Request body: { "name": "Alice", "age": 30, "extra": "value" }

medium

A. The ValidationPipe should have forbidNonWhitelisted to throw error on extra props

B. The whitelist option removes the extra property silently

C. The ValidationPipe is missing transform: true to convert types

D. The extra property causes a validation error

Solution

1. Step 1: Understand whitelist behavior

   Whitelist removes properties not in DTO silently without error.

2. Step 2: Check how to throw error on extra props

   To throw error on extra properties, forbidNonWhitelisted: true must be set.

3. Final Answer:

   The ValidationPipe should have forbidNonWhitelisted to throw error on extra props -> Option A

4. Quick Check:

   forbidNonWhitelisted throws error on extra props [OK]

Hint: Use forbidNonWhitelisted to reject extra properties with error [OK]

Common Mistakes:

• Thinking whitelist throws error by default
• Ignoring need for forbidNonWhitelisted option
• Confusing whitelist with transform option

5. You want to ensure that your NestJS API only accepts properties defined in your DTO, automatically converts input types, and throws an error if extra properties are sent. Which ValidationPipe configuration achieves this?

hard

A. new ValidationPipe({ whitelist: true, transform: true })

B. new ValidationPipe({ whitelist: true, transform: true, forbidNonWhitelisted: true })

C. new ValidationPipe({ transform: true, skipMissingProperties: true })

D. new ValidationPipe({ whitelist: true, forbidNonWhitelisted: true })

Solution

1. Step 1: Identify needed options

   Whitelist removes extra props, transform converts types, forbidNonWhitelisted throws error on extra props.

2. Step 2: Match options to requirements

   Only new ValidationPipe({ whitelist: true, transform: true, forbidNonWhitelisted: true }) includes all three: whitelist, transform, and forbidNonWhitelisted.

3. Final Answer:

   new ValidationPipe({ whitelist: true, transform: true, forbidNonWhitelisted: true }) -> Option B

4. Quick Check:

   Whitelist + transform + forbidNonWhitelisted = strict validation [OK]

Hint: Combine whitelist, transform, forbidNonWhitelisted for strict validation [OK]

Common Mistakes:

• Omitting forbidNonWhitelisted to throw errors
• Forgetting transform for type conversion
• Using skipMissingProperties instead of forbidNonWhitelisted