Prisma how to run other queries as findMany about casl

[stalniy]

Casl wraps everything in OR because in case of multiple rules for the same action/subject type they are OR-ed.

I can optimize it for single OR condition but then your whole app may be broken because at some point in the future you may add additional condition.

So I’d not rely on the shape of the conditions casl returns you back

[13uraksahin]

Hmm, I got the point. Correct as fundamental.

However, without any extra or (or anything else), we can also add our own AND or OR conditions, and with the proper documentation, this can be understood and used by developers much more easily. Should it really be OR-ed by default while I can write myself? Because we have the @casl/prisma package, but we cannot use with the prisma if we won't use findMany or findFirst, (I mean we really cannot use with prisma). Also, I am not sure, but this can be done with casl because doc only shows how to write findMany and this update won't affect findMany.

What I suggest makes us to be able to:
We can add all types of conditions to the conditions inside can/cannot which will create accessibleBy(ability)
We can add all types of conditions to the prisma where object
We can combine both of above
Won't violate the fundamentals
Won't break the apps written with documentation

I think this is easier while brings much more possibilities to the code. And I think it does not violates the fundamentals. We still create.

[saboorajat]

Hey,
I want to have condition which will check that if last_name is present then it must be Tony but as it's update API we might not send last_name hence the other condition. It would have been nice if $or was available for use. Also, i noticed if i want to have multiple conditions example first_name then ability.relevantRuleFor(inputAction as ACTIONS, subject(String(subjectName), { [key]: value })
will be true always

{
            type: "can",
            action: ACTIONS.UPDATE_INPUT,
            subject,
            fields: ["first_name", "last_name", "id", "email"],
            condition: { last_name: "Tony" },
        },
        {
            type: "can",
            action: ACTIONS.UPDATE_INPUT,
            subject,
            fields: ["first_name", "last_name", "id", "email"],
            condition: { last_name: { $exists: false } },
        },