The position of 'whereHas' in a query builder matters, is it intended?

[kondi3]

Laravel 11.x
PHP 8.3

I recently had the need to query resources based on the following factors:

• The resource belongs to the authenticated user.
• Or the resource has a related resource (defined as a hasMany relationship) which belongs to the authenticated user.

So I used an orWhereHas method like so:

$organisations = Organisation::query()
    ->where('user_id', $id)
    ->orWhereHas('members', function ($query) {
           $query->where('user_id', $id);
    }) ;

This works fine, however the problem came when I needed to add more filtering logic specific to the Organisation resource. I noticed that any filter I would apply after the orWhereHas wouldn't take any effect on the result. For example if I need to get the last resource, this will still return the first resource. If I apply another where clause, this won't take any effect on the result it will only consider up to the orWhereHas method.

It finally worked as I intended when I had placed the whereHas method as the first filter and had orWhere method as the second filter, any other subsequent filter I applied after this specific order would take effect on the result like so:

$organisations = Organisation::query()
    ->whereHas('members', function ($query) {
           $query->where('user_id', $id);
    }) 
    ->orWhere('user_id', $id);

This specific ordering of the whereHas method, is this how it is supposed to work? or i'm missing something for it to work the way i wanted it to while using the first way of things (disregarding order)?