What is the difference between @Body(), @Body('field'), and using a full DTO class in NestJS?

Q: What is the difference between @Body(), @Body('field'), and using a full DTO class in NestJS?

// @Body() with no arg — entire raw body, no validation @Post() create(@Body() body: unknown) { // body is the full parsed JSON — no class-validator rules applied } // @Body('name') — single field, no validation @Post() createUser(@Body('name') name: string) { // only the 'name' field — other fields are ignored // no validation on the field itself } // @Body() with DTO — correct production pattern export class CreateUserDto { @IsEmail() email: string; @MinLength(8) password: string; } @Post() create(@Body() dto: CreateUserDto) { // ValidationPipe validated and transformed dto before this runs // dto is a typed CreateUserDto instance, not a plain object // whitelist: true has stripped any unknown properties } @Body() with no arg — use only for untyped webhooks or fully dynamic payloads. @Body('field') — useful for simple single-field extractions but provides no validation. @Body() with DTO class + ValidationPipe — always the correct approach for production endpoints. Global ValidationPipe with whitelist: true strips unknown properties before the handler receives the body. With transform: true, the body is converted to a typed DTO class instance, not just a plain object.

Difficulty: 5/10

request payload handling, DTO validation, NestJS decorators

@Body() with no argument injects the entire raw parsed body with no validation. @Body('field') extracts a single field from the body without validating it. @Body() with a DTO class combined with ValidationPipe is the correct production pattern — it validates, transforms, and strips unknown properties before the handler runs.

@Body() variations and when to use each

Body extraction patterns comparison:

1
@Body() with no arg — use only for untyped webhooks or fully dynamic payloads.
2
@Body('field') — useful for simple single-field extractions but provides no validation.

What is the difference between @Body(), @Body('field'), and using a full DTO class in NestJS?

Difficulty: 5/10

request payload handling, DTO validation, NestJS decorators

@Body() with no argument injects the entire raw parsed body with no validation. @Body('field') extracts a single field from the body without validating it. @Body() with a DTO class combined with ValidationPipe is the correct production pattern — it validates, transforms, and strips unknown properties before the handler runs.

@Body() variations and when to use each

Body extraction patterns comparison:

1
@Body() with no arg — use only for untyped webhooks or fully dynamic payloads.
2
@Body('field') — useful for simple single-field extractions but provides no validation.

What is the difference between @Body(), @Body('field'), and using a full DTO class in NestJS?

What is the difference between @Body(), @Body('field'), and using a full DTO class in NestJS?

Scenario Questions

Follow-up Questions