You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of using a raw stack with simple push and pops we should assign each entry a GUID so that we can have more controlled revoke behavior for easier mixing of block and ! syntax's.
allow_phi! should return a GUID
disallow_phi! should accept an optional GUID to remove
allow_phi and disallow_phi blocks should track the GUID they create and then revoke that particular access.
This will better support weird mixes like the following, with at least consistent behavior (even if we still don't recommend it):
Instead of using a raw stack with simple push and pops we should assign each entry a GUID so that we can have more controlled revoke behavior for easier mixing of
block
and!
syntax's.allow_phi!
should return a GUIDdisallow_phi!
should accept an optional GUID to removeallow_phi
anddisallow_phi
blocks should track the GUID they create and then revoke that particular access.This will better support weird mixes like the following, with at least consistent behavior (even if we still don't recommend it):
The text was updated successfully, but these errors were encountered: