Stop Hand-Rolling Input Checks in NestJS: Use ValidationPipe as a Contract
Stop writing manual input checks. Use NestJS ValidationPipe with class-validator to enforce request contracts, transform payloads, and centralize error formatting.
Loading…
ReadMeFeed / Community knowledge
#validationpipe
Real questions. Useful conversations. Find the people who know your stack.
nestjsDiagnosing NestJS Global Validation Pipe Not Throwing Errors on Invalid DTOs
Learn why NestJS global ValidationPipe may let invalid DTOs reach your controller and how to systematically diagnose and fix the issue.
Configuring NestJS ValidationPipe for DTO Validation with class-validator and class-transformer
Learn how to install, configure, and test NestJS ValidationPipe with class-validator and class-transformer to validate and transform incoming request payloads into strongly-typed DTO instances.
Building a Reusable Offset Pagination Pattern in NestJS with ValidationPipe and TypeORM
Learn how to turn string query params into type‑safe pagination in NestJS using a ValidationPipe‑transformed DTO and TypeORM’s findAndCount, plus the trade‑offs of offset pagination.
Implementing Global Request Validation in NestJS with ValidationPipe
Set up a ValidationPipe globally to enforce DTO constraints, strip unknown fields, transform payloads, and customize error responses.
Hardening NestJS REST Controllers with ValidationPipe
Enforce payload shape and type safety at the application edge using ValidationPipe and class-validator to prevent invalid data from reaching your service layer.
ValidationPipe whitelist default shift in NestJS 9 and the open question on forbidUnknownValues
The shift in NestJS 9 changed the ValidationPipe’s default whitelist option from false to true, causing unknown properties in DTO payloads to be stripped silently. Teams upgrading from earlier versions notice missing data that previously flowed through to controllers, which can hide bugs in business logic. The goal is to determine whether the framework shoul
NestJS 10 ValidationPipe Date Transformation Change: Impact on DTO Date Fields
When upgrading to NestJS 10, the global ValidationPipe no longer automatically converts incoming ISO‑8601 date strings into Date objects unless the transform option is enabled. With transform:true, class‑transformer will instantiate a Date but retains the original timezone offset unless explicitly configured to shift to UTC. Because NestJS provides no timezo