Skip to content

fix: example heading under new enemy problem section #224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 3, 2024
Merged

fix: example heading under new enemy problem section #224

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/spicedb/concepts/zanzibar.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ This term was first introduced in the Zanzibar paper where solving this problem
>Specifically, our clients care about preventing the "new enemy" problem, which can arise when we fail to respect the ordering between ACL updates or when we apply old ACLs to new content.
>Consider these two examples:
>
>**Example B: Misapplying old ACL to new content**
>**Example A: Neglecting ACL update order**
>
>1. Alice removes Bob from the ACL of a folder;
>2. Alice then asks Charlie to move new documents to the folder, where document ACLs inherit from folder ACLs;
Expand Down