hello) As I understand, the LookupResources2 method from version v1.35.0 has not been implemented yet in the authzed/authzed-go library, correct?

It's not a new API, it's a new dispatch API, so there are no changes for you. You just need to enable the flag

ok, super)

no

thank you)

please report if you see any improvements!

i have tested lookup with 2k relations per 10 objects definition project { relation owner: user relation parent: folder relation viewer: user | link | group relation editor: user | link | group relation signer: user relation commenter: user | link | group relation filler: user permission can_view = viewer + can_edit + viewer->membership + parent + parent->can_view + can_fill + can_comment + can_sign permission can_edit = editor + editor->membership + parent + parent->can_edit + can_all permission can_sign = signer + can_fill permission can_all = owner permission has_access = can_view permission can_comment = commenter + can_edit + parent + parent->can_comment + commenter->membership permission can_fill = filler } i added 10 users with 2k user->owner->project relations per each and after this i did lookup projects per each user with filter by relation can_view and i don`t see any profit)) https://cdn.discordapp.com/attachments/1268155654678515723/1269210350411059341/Screenshot_2024-08-03_at_10.28.40.png?ex=66af3bc0&is=66adea40&hm=7c1318b68ce1a6c78e92604be6fabb88ccbb526aa27617e35ee2b3ae926d40f0&

@Joey ☝️

there won't be any improvements; you're not using any intersections, exclusions or caveats