Repository navigation
[Feature Request] Allow for Prisma enums in validation rules #1211
Description
Activity
Hey @nwidynski , thanks for filing this. Do you mind providing a ZModel snippet showing how you want to use it? Thanks!
Got it. Yes, string and enum can be compatible for comparison.
Reacted by Nikolas SchröterWe‘re especially looking for the in operator which would probably translate to:
Object.values(PostStatus).includes(value)
I actually don't get why this is necessary. Making
statusof type PostStatus instead of String would already validate the type natively in prisma. No need for in operator in zenstack in this case.2 years later
The
==comparison currently works with enums as long as you don't fully qualify the enum and instead reference the field directly.@@validate(status == PostStatus.ACTIVE) // ❌ @@validate(status == ACTIVE) // ✅
I've implemented support for the
inoperator in #2807
Is your feature request related to a problem? Please describe.
While Zenstack is already offering great validation capabilities, it would be nice if it were possible to use Prisma enums
inside a validate block, for example with an
inoperation. This would allow for an always-in-sync validation instead of relying on manual updates in both codebase and validation rules.One might ask why not set the field as the enum? The answer to that being that working with primitives is easier to migrate and also better supported across third party vendors, like Hasura GraphQL.
Describe the solution you'd like
Allow for Prisma enums to be referenced in validations rules, especially with the
inoperator.Describe alternatives you've considered
Additional context