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
Currently, the filter operation runs on all entities by default. It would be beneficial to introduce a new feature that allows users to specify a scope of entity-ids for the filter operation.
For example, given the following schema:
entity project {
relation workspace @workspace;
relation admin @user @team#member;
relation member @user @team#member;
relation guest @user @team#member;
permission create_task := workspace.owner or workspace.admin
or admin or member;
permission edit := workspace.owner or workspace.admin or admin;
permission view := admin or member or guest or workspace.view;
}
entity task {
relation project @project;
relation assignee @user;
permission view := project.view;
}
It would be great to allow a way to filter which tasks of project y that a user can view. One way of doing that would be first querying all tasks in that project and then passing into the LookupEntity to filter for only those tasks.
The text was updated successfully, but these errors were encountered:
Currently, the filter operation runs on all entities by default. It would be beneficial to introduce a new feature that allows users to specify a scope of entity-ids for the filter operation.
For example, given the following schema:
It would be great to allow a way to filter which tasks of project y that a user can view. One way of doing that would be first querying all tasks in that project and then passing into the LookupEntity to filter for only those tasks.
The text was updated successfully, but these errors were encountered: