✨ The fork of Zod Prisma generator for using with nestjs-zod ✨

Ecosystem

Package	About
nestjs-zod	A tools for integrating Zod into your NestJS application
nestjs-zod-prisma	Generate Zod schemas from your Prisma schema

Table of Contents

1. About The Project
   • Built With
2. Getting Started
   • Prerequisites
   • Installation
3. Usage
   • JSDoc Generation
   • Extending Zod Fields
   • Importing Helpers
     • Custom Zod Schemas
   • JSON Fields
4. Examples
5. Roadmap
6. Contributing
7. License
8. Contact

About The Project

Zod Prisma doesn't work well with nestjs-zod and its author has been inactive for a long time - so I created this fork to fix the problems that I suffered from.

To work better with nestjs-zod, this library provides a little different API for Prisma rich comments directives.

You can use @z.string().etc() for specifying different nestjs-zod/z schemas, @z&.something().etc() for applying a new methods on the schema and @z.from(imports.MyPasswordSchema) for using your own schemas.

Also, this library generates DTOs for better NestJS integration. It's done using createZodDto from nestjs-zod.

And we still support the JSDoc comments.

Built With

• dts-cli
• Zod
• Based on this gist

Getting Started

To get a local copy up and running follow these simple steps.

Prerequisites

• prisma - ^3.0.0
• nestjs-zod - ^0.4.4

Installation

0. Ensure your tsconfig.json enables the compiler's strict mode. Zod requires it and so do we, you will experience TS errors without strict mode enabled

1. Add nestjs-zod-prisma as a dev dependency

   1yarn add -D nestjs-zod-prisma

2. Add the nestjs-zod-prisma generator to your schema.prisma

   1generator zod {
   2  provider                 = "nestjs-zod-prisma"
   3  output                   = "./src/zod" // (default) the directory where generated zod schemas will be saved
   4
   5  relationModel            = true // (default) Create and export both plain and related models.
   6  // relationModel         = "default" // Do not export model without relations.
   7  // relationModel         = false // Do not generate related model
   8
   9  generateDto              = true // (default) Generate DTOs for NestJS
   10
   11  modelCase                = "PascalCase" // (default) Output models using pascal case (ex. UserModel, PostModel)
   12  // modelCase             = "camelCase" // Output models using camel case (ex. userModel, postModel)
   13
   14  modelSuffix              = "Model" // (default) Suffix to apply to your prisma models when naming Zod schemas
   15
   16  dtoCase                = "PascalCase" // (default) Output DTOs using pascal case (ex. UserDto, PostDto)
   17  // dtoCase             = "camelCase" // Output DTOs using camel case (ex. userDto, postDto)
   18
   19  dtoSuffix              = "Dto" // (default) Suffix to apply to your prisma models when naming DTOs
   20
   21  // useDecimalJs          = false // (default) represent the prisma Decimal type using as a JS number
   22  useDecimalJs             = true // represent the prisma Decimal type using Decimal.js (as Prisma does)
   23
   24  imports                  = null // (default) will import the referenced file in generated schemas to be used via imports.someExportedVariable
   25
   26  // https://www.prisma.io/docs/concepts/components/prisma-client/working-with-fields/working-with-json-fields#filtering-by-null-values
   27  prismaJsonNullability    = true // (default) uses prisma's scheme for JSON field nullability
   28  // prismaJsonNullability = false // allows null assignment to optional JSON fields
   29}

3. Run npx prisma generate or yarn prisma generate to generate your zod schemas

4. Import the generated schemas form your selected output location

Usage

JSDoc Generation

Rich-comments in the Prisma schema will be transformed into JSDoc for the associated fields:

Note: make sure to use a triple-slash. Double-slash comments won't be processed.

1model Post {
2  /// The unique identifier for the post
3  /// @default {Generated by database}
4  id String @id @default(uuid())
5
6  /// A brief title that describes the contents of the post
7  title String
8
9  /// The actual contents of the post.
10  contents String
11}

Generated code:

1export const PostModel = z.object({
2  /**
3   * The unique identifier for the post
4   * @default {Generated by database}
5   */
6  id: z.string().uuid(),
7  /**
8   * A brief title that describes the contents of the post
9   */
10  title: z.string(),
11  /**
12   * The actual contents of the post.
13   */
14  contents: z.string(),
15})

Using different Zod type

You can also use the @z keyword in rich-comments in the Prisma schema to specify your Zod schema:

1model User {
2  id String @id @default(uuid()) /// @z.string().uuid()
3
4  /// @z.string().min(8).max(20)
5  username String
6
7  /// @z.password().atLeastOne('digit').atLeastOne('lowercase').atLeastOne('uppercase').min(8).max(100)
8  password String
9}

Generated code:

1export const UserModel = z.object({
2  id: z.string().uuid(),
3  username: z.string().min(8).max(20),
4  password: z
5    .password()
6    .atLeastOne('digit')
7    .atLeastOne('lowercase')
8    .atLeastOne('uppercase')
9    .min(8)
10    .max(100),
11})

Importing Helpers

Sometimes its useful to define a custom Zod preprocessor or transformer for your data. nestjs-zod-prisma enables you to reuse these by importing them via a config options. For example:

1generator zod {
2  provider      = "nestjs-zod-prisma"
3  output        = "./src/zod"
4  imports       = "../zod-schemas"
5}
6
7model User {
8  username  String /// @z.string().refine(imports.isValidUsername)
9}

The referenced file can then be used by simply referring to exported members via imports.whateverExport. The generated zod schema files will now include a namespaced import like the following.

1import * as imports from '../../src/zod-schemas'

Using custom Zod schema

Use combination of z.from and imports to apply your custom Zod schema:

1model User {
2  id String @id @default(uuid())
3  username String
4
5  /// @z.from(imports.MyPasswordSchema)
6  password String
7}

JSON Fields

JSON fields in Prisma disallow null values. This is to disambiguate between setting a field's value to NULL in the database and having a value of null stored in the JSON. In accordance with this nestjs-zod-prisma will default to disallowing null values, even if your JSON field is optional.

If you would like to revert this behavior and allow null assignment to JSON fields, you can set prismaJsonNullability to false in the generator options.

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes (git commit -m 'Add some AmazingFeature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.

Contact

Mohammad Abdalrazzak - mohrazzak7@gmail.com

Project Link: https://github.com/mohrazzak/nestjs-zod-prisma