Adding a validation pipe to add dtos #11
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OsamaRab3
reviewed
Oct 23, 2025
src/main.ts
Outdated
Comment on lines
7
to
16
|
|
||
| /* | ||
| Warning for the AC team: | ||
| When whitelist is true, NestJS will automatically remove any properties from the incoming data that are not defined in your DTO class. | ||
| When forbidNonWhitelisted is true, instead of removing the extra properties, NestJS will throw an error if it finds any field not defined in your DTO. | ||
| When transform is true, NestJS will automatically transform payloads to be objects typed according to their DTO classes. | ||
| # hint for the future: while making users module add a dto folder inside users module and define your dtos there. | ||
| # TODO: add common dtos for requests and responses | ||
| */ |
Member
There was a problem hiding this comment.
Pleas remove all comment here
gazzaar
reviewed
Oct 23, 2025
Member
gazzaar
left a comment
gazzaar
left a comment
There was a problem hiding this comment.
Looks good! Please remove the comments, as the details have already been explained in the pr description.
OsamaRab3
approved these changes
Oct 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces input validation for incoming requests using NestJS's
ValidationPipe, and adds the required dependencies for class-based validation and transformation. These changes help ensure that only expected and properly formatted data is accepted by the application.Input validation and transformation:
Configured a global
ValidationPipeinsrc/main.tsto automatically validate and transform incoming request payloads according to DTO classes, enforce whitelisting, and forbid non-whitelisted properties.When whitelist is true, NestJS will automatically remove any properties from the incoming data that are not defined in your DTO class.
When forbidNonWhitelisted is true, instead of removing the extra properties, NestJS will throw an error if it finds any field not defined in your DTO.
When transform is true, NestJS will automatically transform payloads to be objects typed according to their DTO classes.
Dependency additions:
class-transformerandclass-validatorpackages topackage.jsonto support DTO-based validation and transformation.