A few ideas

[kamilmysliwiec]

Hey @risen228, great job on creating this package! NestJS creator here.

I recently started working on the @nestjs/zod package to simplify the integration between the two (Nest and Zod), and then I came across your package and noticed that it already provides several features I planned to add to the official library (great job!)

So I'd like to suggest a few improvements/questions, just in case you have some time:

• instead of patching the @nestjs/swagger, you could add a static _OPENAPI_METADATA_FACTORY method to your Zod DTO classes (see screenshot below - from my local project)
  
• guards shouldn't be used for validating input payload (incoming dtos)
• any reason Zod isn't declared as a peer dependency?
• ValidationPipe could expose a few additional options (screenshot form my local project)

Fantastic job again!

[risen228]

Thanks for your suggestions! I will try to find a time to implement it. Doesn't have much at this moment :/

As I remember, the reason why Zod was removed from peers is /frontend library scope, which doesn't require Zod. It would be a right way to split this library in multiple, but nestjs-zod historically is the single package, so it's not easy to do this.

I hope you will come out with the official Zod + NestJS integration soon =)

P.S. As I see, Zod is specified in peer deps, but I think the range is not good, I did it hastily and it should be fixed to allow only ^3 and ^4 versions of Zod

[Scalahansolo]

@kamilmysliwiec Interesting to see that your thinking about / working on an official zod package?

With the existence of this package, is your thought this package would become the official recommendation for using Zod with NestJS, or do you still plan to build out an official @nestjs/zod package?

[oskarstucki]

@kamilmysliwiec I would also be interested in knowing 👍

[DavidVaness]

@BenLorantfy excited you started maintaining this package. Given @kamilmysliwiec idea to make an official package, what about transferring it to the nestjs org to ensure this stays maintained going forward? I bet you can keep the role of maintainer, but this would ensure stability going forward

Either way, great you reopened this issue 👍🏼

[BenLorantfy]

@DavidVaness I think an official package is a good idea, but I think it makes sense to implement some of the suggestions from the OP first to get it aligned with nestjs recommendations