Given schema,
definition user {}
definition account {
relation parent: account
relation reader: user
permission read = reader + parent->read
}
get-permission-paths for permission read = reader + parent->read only returns the direct reader path, not the recursive parent->read arrow.- That matches the over-broad permission-eid cycle check in indexed.clj (line 111).
- Because that arrow path is dropped, can? and lookup-subjects do not inherit read from root to child or grandchild.
Fix for over-broad cycle detection in progress, that was dropping some arrow paths at runtime.
Given schema,
get-permission-pathsforpermission read = reader + parent->readonly returns the direct reader path, not the recursive parent->read arrow.Fix for over-broad cycle detection in progress, that was dropping some arrow paths at runtime.