-
-
Notifications
You must be signed in to change notification settings - Fork 7.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with standard-schema #14539
Comments
Notably, there is an issue open on class-validator side around this topic as well: |
I like the ideia but I think this should start as a 3rd-party lib to see community's adoption |
I guess there's nothing we can do until class-validator supports the standard schema too (to avoid breaking changes) |
Unfortunately, the class-validator isn't updated much anymore。typestack/class-validator#1775 |
@0x0bit well |
But he didn't spend any more time in the repository; the latest update was only a month ago. |
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
There are numerous schema validators out there. This has spawned an ecosystem around NestJS with various integrations such as nestjs-valibot and many others.
Describe the solution you'd like
NestJS could support stanadard-schema which recently hit 1.0.0:
With that a commonly shared
ValidationPipe
could be offered directly from the framework instead of copy/pasting the integrations from the docs site.Teachability, documentation, adoption, migration strategy
Guide on how to accept Standard Schema: https://standardschema.dev/#how-do-i-accept-standard-schemas-in-my-library
ValidationPipe
that is compatible with standard-schemaValidationPipe
can be utilised with different schema librariesWhat is the motivation / use case for changing the behavior?
I think it makes NestJS more future-proof with any future schema/validation library that might come
The text was updated successfully, but these errors were encountered: