Nikolas Schröter
Nikolas Schröter
> Maybe something like "partial models" can mitigate this problem? Like: > > ```prisma > model Post { > id Int @id > title String > } > > model...
> > > Maybe something like "partial models" can mitigate this problem? Like: > > > > > > > > > > > > > > > > >...
@ymc9 This would be a short example with some options for the validate API. ``` enum PostStatus { DRAFT ACTIVE CANCELLED } model Post { id String @id status String...
We‘re especially looking for the in operator which would probably translate to: Object.values(PostStatus).includes(value)
@Eliav2 It's mentioned at the bottom of the issue description. Also both the `@@validate` and the `in` operator exist already, just without compatibility for enum fields. No new operator would...
@JamieMason Awesome, we aren't ready just yet to switch to v14 due to lack of `list-mismatches`. Also does this support `sameRange` policy? Some dependencies are related but not for an...
@JamieMason That looks great, just upgraded 👍 As far as 3.) was concerned, i was asking whether its possible to relax the version matching within a group to allow for...
@JamieMason Works great!
@ymc9 @jiashengguo One solution that has been on my mind lately was whether it would be possible to use computed fields inside access policies by defining them as ignored columns...
> > @ymc9 @jiashengguo One solution that has been on my mind lately was whether it would be possible to use computed fields inside access policies by defining them as...