Closed baenio closed 6 months ago
There is of course a workaround for that, but I think, that it should still be possible to write it like initially. Especially the allow
policy will be much longer, which will lead to unreadability.
// workaround, which will work
@@allow("update", future().id == id)
Description and expected behavior While writing the policies, I found out that the update permission in my @@deny is not working as expected. The following two policies will still update the
id
:I also found out, that I can't run
npx zenstack generate
, when I write it like this:Environment: