NestJs自定义Validator注入Repository返回undefined问题求助

核心原因 #

class-validator 默认不会自动复用 NestJS 的依赖注入容器，导致你的UsernameAlreadyExistsConstraint类无法通过构造函数正确注入UserRepository，最终出现this.userRepository为undefined的情况。

正确解决步骤 #

1. 将验证器类注册为模块Provider #

在你的UserModule（或对应业务模块）中，把UsernameAlreadyExistsConstraint添加到providers数组，让Nest的DI容器能够管理这个类：

import { Module } from '@nestjs/common';
import { TypeOrmModule } from '@nestjs/typeorm';
import { User } from './user.entity';
import { UsernameAlreadyExistsConstraint } from './username.validator';

@Module({
  imports: [TypeOrmModule.forFeature([User])],
  providers: [UsernameAlreadyExistsConstraint],
  exports: [UsernameAlreadyExistsConstraint] // 若其他模块需使用该验证器，需添加导出
})
export class UserModule {}

2. 配置class-validator使用Nest的DI容器 #

在main.ts中通过useContainer将Nest的容器绑定到class-validator，注意使用当前推荐的配置项而非已废弃的fallback：

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
import { ValidationPipe } from '@nestjs/common';
import { useContainer } from 'class-validator';

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  
  // 绑定Nest根模块容器到class-validator
  useContainer(app.select(AppModule), { fallbackOnErrors: true });
  
  app.useGlobalPipes(new ValidationPipe({
    transform: true,
    whitelist: true,
  }));
  
  await app.listen(3000);
}
bootstrap();

3. 验证器类优化（可选） #

将异步验证逻辑改为async/await风格，提升代码可读性，同时添加@Injectable装饰器明确标记类为可注入：

import { registerDecorator, ValidationOptions, ValidatorConstraint, ValidatorConstraintInterface, ValidationArguments } from 'class-validator';
import { InjectRepository } from '@nestjs/typeorm';
import { Repository } from 'typeorm';
import { User } from './user.entity';
import { Injectable } from '@nestjs/common';

@ValidatorConstraint({ async: true })
@Injectable()
export class UsernameAlreadyExistsConstraint implements ValidatorConstraintInterface {
  constructor(
    @InjectRepository(User)
    private userRepository: Repository<User>,
  ) {}

  async validate(userName: string, args: ValidationArguments) {
    const user = await this.userRepository.findOneBy({ username: userName });
    return !user; // 存在用户则返回false（验证失败），不存在则返回true（验证通过）
  }
}

export function UsernameAlreadyExists(validationOptions?: ValidationOptions) {
  return function (object: unknown, propertyName: string) {
    registerDecorator({
      target: object.constructor,
      propertyName: propertyName,
      options: validationOptions,
      constraints: [],
      validator: UsernameAlreadyExistsConstraint,
    });
  };
}

关键注意事项 #

• 验证器类必须加入模块的providers数组，否则Nest无法为其注入依赖
• useContainer需传入app.select(AppModule)，确保使用根模块的DI容器实例
• @Injectable装饰器是显式标记类可注入的良好实践，避免DI容器识别异常

内容的提问来源于stack exchange，提问作者Santiago Capdevila