There is an open feature request for Prisma to support runtime model validation directly at the Schema level. Alternatively, you can leverage the Client Extensions to perform validation. There is an example in this blog post that shows how to perform custom runtime validation.

you have three solutions for it: Continue Using DTOs, Custom Validation Pipe, hybrid:

The decision largely depends on your project's specific needs and your team's familiarity with these patterns. If maintaining a clear separation and leveraging existing NestJS features is important, continue using DTOs. If reducing redundancy is a priority, consider the dynamic DTO generation or custom validation pipe approach.

   import { CallHandler, ExecutionContext, Injectable, NestInterceptor } from '@nestjs/common';
import { map } from 'rxjs/operators';

@Injectable()
export class TransformInterceptor implements NestInterceptor {
  intercept(context: ExecutionContext, next: CallHandler<any>) {
    const request = context.switchToHttp().getRequest();
    request.body = new TodoCreateDto(request.body.title, request.body.description);
    return next.handle().pipe(map(data => data));
  }
}