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
Is your feature request related to a problem? Please describe.
We often require to query multiple permission on multiple resource for a subject and currently Permify doesn't have any way to do it in single request and multiple requests are not efficient.
Describe the solution you'd like
It would be great if Permify can provide an endpoint for bulk permission check.
Describe alternatives you've considered
I checked subject permission list and found it uses same check() internally for all the actions for a resource and a subject which is not the best but better than multiple requests in some cases.
However, it's great if Permify can implement some more efficient technique to do reverse lookup.
The text was updated successfully, but these errors were encountered:
Anyone knows what would be required to make this work in the code?
Had a quick look but not sure if it's as simple as adding a new endpoint where you can pass tuples and get an array/stream back? Which internally only is a wrapper around the endpoint for the single lookup? Or is there a more efficient way to do this?
Is your feature request related to a problem? Please describe.
We often require to query multiple permission on multiple resource for a subject and currently Permify doesn't have any way to do it in single request and multiple requests are not efficient.
Describe the solution you'd like
It would be great if Permify can provide an endpoint for bulk permission check.
Describe alternatives you've considered
I checked subject permission list and found it uses same
check()
internally for all the actions for a resource and a subject which is not the best but better than multiple requests in some cases.However, it's great if Permify can implement some more efficient technique to do reverse lookup.
The text was updated successfully, but these errors were encountered: