$and and $or restricted filters are not forced when using relations

[ItsReddi]

Request

?filters[field1][$eq]=<value1>
&filters[$and][0][relationName][fieldX][$eq]=<valueX>
&filters[$and][1][relationName][fieldY][$eq]=<valueY>

Config

BaseModel (Where filters are applied to) has the following $filters

protected array $filters = [
        EqualFilter::class,
        NotEqualFilter::class,
        AndFilter::class,
        OrFilter::class,
    ];

The Relation model has:

protected array $filters = [
        EqualFilter::class,
        NotEqualFilter::class,
    ];

Result

Even if not defined in Relation model. The $and and $or filters are applied.

Also the other way around, if we do not apply and & or filters to base model but on relation model, the above query will not filter with $and. It is also not possible to change the request for that case to:

?filters[field1][$eq]=<value1>
&filters[relationName][$and][0][fieldX][$eq]=<valueX>
&filters[relationName][$and][1][fieldY][$eq]=<valueY>

Expected

Filter restrictions are applied, when working with relations

[abbasudo]

Hello, thanks for your clear report. unfortunately, this is true for any relation filter. in this, line purity iterates throw the filter and as long as it finds some valid filter it returns. this behavior is correct as long as we don't have any relation filter.

the validate function should be changed to something like this function which considers the model.
any idea how to do this?