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.

Note: I’m one of the authors of Remult

With Remult you have one TypeScript class (per entity) which serves as a single source of truth for the API endpoints, API client and ORM. It can also run TypeScript validation code, defined in entity decorators, in both the frontend (e.g. before mutation requests are sent) and the backend.

Only caveat is that while the current version of Remult can be used to expose a GraphQL endpoint, the current API client only supports RESTful. Other than that I think it can fit nicely in your stack.

Hello @MohamadrezaKazemian 👋

You can use libraries like Joi or Zod to validate your data. Joi and Zod has inbuilt functions like .email() to validate if a string is a valid email address. You can use the min() and max() functions of these libraries to validate the length of the password field.

Also, if you don't want to use these libraries you can use a regex to validate if the provided string is an email and also to check the length of the password.

It would look something like this:

        // Validate email
        if (!/^\S+@\S+$/.test(data.email)) {
            return res.status(400).json({ message: 'Invalid email' });
        }

        // Validate password
        if (data.password.length < 5 || data.password.length > 10) {
            return res.status(400).json({ message: 'Password must be between 5 and 10 characters' });
        }