How do you use validation groups with class-validator to apply different rules for create vs update operations in NestJS?

Q: How do you use validation groups with class-validator to apply different rules for create vs update operations in NestJS?

export class UserDto { @IsString({ groups: ['create', 'update'] }) @IsNotEmpty({ groups: ['create'] }) // required on create only name?: string; @IsEmail({ groups: ['create'] }) @IsNotEmpty({ groups: ['create'] }) // required on create only email?: string; @MinLength(8, { groups: ['create', 'update'] }) @IsOptional({ groups: ['update'] }) // optional on update password?: string; } // Extend ValidationPipe for each group @Injectable() export class CreateValidationPipe extends ValidationPipe { constructor() { super({ groups: ['create'], whitelist: true, transform: true }); } } @Injectable() export class UpdateValidationPipe extends ValidationPipe { constructor() { super({ groups: ['update'], whitelist: true, transform: true, skipMissingProperties: true, }); } } // Controller @Post() create(@Body(CreateValidationPipe) dto: UserDto) {} @Patch() update(@Body(UpdateValidationPipe) dto: UserDto) {} Decorators without a groups option apply to ALL groups — always specify groups explicitly. Use skipMissingProperties: true on update groups so absent fields are not treated as errors. Groups are passed as a string array — multiple groups can be active simultaneously. A decorator with groups: ['create'] is completely ignored during update validation. For simple create/update patterns, separate CreateDto and UpdateDto classes (with PartialType) is often cleaner.

Difficulty: 5/10

validation groups, DTOs, NestJS pipes

class-validator supports groups — decorators declare which groups they belong to, and ValidationPipe is configured with a specific group to run. Extend ValidationPipe with different group settings for create (all fields required) and update (all fields optional) handlers.

Validation groups for create and update DTOs

Validation group patterns:

1
Decorators without a groups option apply to ALL groups — always specify groups explicitly.
2

How do you use validation groups with class-validator to apply different rules for create vs update operations in NestJS?

Difficulty: 5/10

validation groups, DTOs, NestJS pipes

class-validator supports groups — decorators declare which groups they belong to, and ValidationPipe is configured with a specific group to run. Extend ValidationPipe with different group settings for create (all fields required) and update (all fields optional) handlers.

Validation groups for create and update DTOs

Validation group patterns:

1
Decorators without a groups option apply to ALL groups — always specify groups explicitly.
2

How do you use validation groups with class-validator to apply different rules for create vs update operations in NestJS?

class-validator supports groups — decorators declare which groups they belong to, and ValidationPipe is configured with a specific group to run. Extend ValidationPipe with different group settings for create (all fields required) and update (all fields optional) handlers.

How do you use validation groups with class-validator to apply different rules for create vs update operations in NestJS?

class-validator supports groups — decorators declare which groups they belong to, and ValidationPipe is configured with a specific group to run. Extend ValidationPipe with different group settings for create (all fields required) and update (all fields optional) handlers.

Scenario Questions

Follow-up Questions