@hodfords/nestjs-validation
nestjs-validation enhances validation in your NestJS projects by providing a customized ValidationPipe that returns custom error messages. This library simplifies error handling by offering localized and user-friendly responses
Installation ๐คโ
Install the nestjs-validation
package with:
npm install @hodfords/nestjs-validation --save
Usage ๐โ
First, create an instance of ValidationPipe
with the desired configuration:
import { ValidationPipe } from '@hodfords/nestjs-validation';
import { ValidateException } from '@hodfords/nestjs-exception';
export const validateConfig = new ValidationPipe({
whitelist: true,
stopAtFirstError: true,
forbidUnknownValues: false,
exceptionFactory: (errors): ValidateException => new ValidateException(errors)
});
Next, set the validation configuration globally in your bootstrap function:
async function bootstrap() {
const app = await NestFactory.create(AppModule);
app.useGlobalPipes(validateConfig);
await app.listen(3000);
}
Customize Validation Errorโ
The original error message provides basic information but lacks detail. With nestjs-validation, you can enhance these errors by adding meaningful context, such as the fieldโs property name, value, and target object.
Original Validation Error
ValidationError {
target: AppDto { stringValue: undefined },
value: undefined,
property: 'stringValue',
children: [],
constraints: { isString: 'stringValue must be a string' }
}
Customized Validation Error
ValidationError {
target: AppDto { stringValue: undefined },
value: undefined,
property: 'stringValue',
children: [],
constraints: {
isString: {
message: '$property must be a string',
detail: { property: 'stringValue', target: 'AppDto', value: undefined }
}
}
}
Exceptionโ
When combined with nestjs-exception, errors are translated into localized messages:
{
"message": "Validate Exception",
"errors": {
"stringValue": {
"messages": ["String Value must be a string"]
}
}
}
License ๐โ
This project is licensed under the MIT License