How to enforce request where subject is an array of user roles?

hello, i have some issues
mainly with the part where i wanted a request that goes something like this

sub: array of user roles
obj: server end point
act: http method

where with sub at least 1 correct role must be present, but seem to struggle with this
ideas?

sub should be user, not roles

hmm so a array of user roles from the user is not possible any other ideas?
not going to add every user in the file

rather split them up in groups

because i would have liked to do a request like

["user", "admin"], /api/posts, POST

or something similar
and only those roles would have access

use BatchEnforce

will take a look thanks

Forgot to follow up
Be able to check multiple requests at omce is verry usefull

I can just construct a request each time with a diffrent role from the user and group check them

Thx a lot

i struggle with finding what i need in the docs, this happens a lot to me
where can i find the part that mentions

for request
user alice read:own

i was talking about th last part where read and own are 2 seperated things binded with a : i know it exist but need more docs about it

wasn't there in casbin do do a quest something like alice, data1, read:any i'm mainly talking about read:any
where they seem 1 thing casbin can read read and any separate or something like that?
i know it exist, but couldn't find it back in the docs

just a seperate question

@.adityanambiar @weshuiz13 for long question, plz create github issue

Long as in, it takes long or sized questions?
I'm just asking where in the docs the part is for using the : in a request
Where casbin can understand a request example i posted above
Where casbin can read read:any as separate words

but this is resolved now

request doesn't support * or : you said, Casbin doesn't handle it in a special way, you need to define your custom function in matcher to handle it

Then why can action:read be done using groups?

I don't know what you are saying about "action:read", you'd better take a look at the docs first, then ask question