When activating a user, I need to ensure that certain optional data in the database is not empty by using class-validator dto. So far, my controller level validations for body, query, and all other aspects have been successful.
The DTO file contains validation rules for checking properties:
export class UserActiveDTO {
@IsNotEmpty()
@IsString()
readonly id: string;
@IsNotEmpty()
@IsString()
readonly name: string;
@IsNotEmpty()
@IsString()
readonly role: string;
//.. other data validations
}
Within the service file, after retrieving the user from the database:
// Retrieving user information and attempting to validate it
let userCanBeActive: boolean = false;
try {
const canActiveUser: UserActiveDTO = user;
// Validating user using class-validator
const vErrors = await validate(canActiveUser, {});
if (vErrors.length > 0) throw vErrors;
userCanBeActive = true;
} catch (error) {
userCanBeActive = false;
}
Despite implementing these validations, the code always sets userCanBeActive as true, even when properties mentioned in the DTO file are missing. What is the best practice for validating such scenarios in NestJS?