Closed baenio closed 4 months ago
@baenie our environment is
Environment:
ZenStack version: 2.1.0 Prisma version: 5.13.0 Database type: Postgresql
Prisma version: 5.13.0 Database type: Postgresql
But I tested all releases. The bug was introduced in v2.0.0.
Thanks for reporting this, guys. I'll try to reproduce and hopefully make a fix soon!
Hi @iamfj @baenie , could you try if the new 2.1.1 release fixed the issue?
Hi @iamfj @baenie , could you try if the new 2.1.1 release fixed the issue?
It seams to work now! Thank you for your fast response! ❤️
Thanks! 🚀
Description and expected behavior After trying to upgrade ZenStack to v2, I discovered a bug when trying to call
/api/model/membership/findMany
(see error message). Every other table was working fine, expect Membership.After some digging I found out, that it was a field level access policy causing the issue:
@deny("read, update", space.memberships?[auth() == user && !(role in [owner, admin, roleManager])])
After removing theread
part, it was working just fine.This policy was working just fine in v1 of ZenStack, but I tried every v2 release and in every version the error occured.
Error
Environment:
Additional context