Igor Šimko

Hey, I'm having same issue. Example of such model would be: ``` model Space { id String @id @default(cuid()) createdAt DateTime @default(now()) updatedAt DateTime @updatedAt name String @unique @db.Text userAccess...

Thanks for suggestion. But I thought that's exactly what ZenStack is made for. I have feeling like something is off either with zmodel or there's bug. I'll try to reproduce...

Hey @ymc9, since I can't include real code/model where my problem occurs I missed one additional relation in example which I shared above. However I managed to replicate an issue...

Hey @ymc9, did you by any chance have time to look into example I provided. It seems like quite a important bug to solve or at least to understand why...

Hey @ymc9, thanks for looking into that and for explanation. > Btw, I'm not sure if the cross-model field comparison is a must-have for your rules @igorsimko This model design...

Hey @ymc9 did you have a chance to look into validator issue? And possibly suggest some workaround other than explicitly including relations?

@israelins85 thanks for suggestion again, but this is very error prone and it makes then whole zenstack need for this use case redundant. Only thing I can think of is...

@ymc9 I think @israelins85 was refering to just always `include` (or add `where`) `UserAccess` to your queries like instead of ``` const shouldBeBot22withTake1 = await prismaEnhanced.spaceEnvironmentBot.findMany({ take: 1, }); ```...

Thanks for explanation, that I don't know. I also tried adding user access directly to user while ehancing prisma and changing condition to: ``` @@allow('read', auth().userAccess?[environmentId == this.environmentId && spaceId==...

Same thing happening to me. Order is reversed and middle frames are even overlapping - Seems like 2 frames are on top each other with some opacity + one frame...