Skip to content

Explain arrow on subject relation #119

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

Closed
wants to merge 3 commits into from
Closed

Explain arrow on subject relation #119

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e790e6d
Explain arrow on subject relation
alechenninger May 16, 2023
005f7f9
Add missing colons
alechenninger May 16, 2023
4320f70
Update schema-lang.md
alechenninger May 23, 2023
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
6 changes: 6 additions & 0 deletions docs/reference/schema-lang.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,6 +214,12 @@ permission can_only_read = reader - writer

Arrows allow for "walking" the heirarchy of relations (and permissions) defined for an object, referencing a permission or relation on the _resulting_ object.

:::info
When using the arrow operator on a subject relation, such as the `group#member` subject relation in the `relation member: user | group#member` example above, the resulting object is the _subject_ of the subject relation, not the relation itself.

That is, an expression like `member->verb` (where `member` was a `group#member`) would reference the `verb` permission on the related `group`, not the `#member`s of the `group`.
:::

For example, imagine a schema where a document is found under a folder:

```zed
Expand Down
Loading