Fix sql query for multifilter

[anddyyyy46]

There was a bug regarding multifilter.

The filters were split depending on whether they had an or operator or an and operator somewhere. However, multifilter may start with an and operator and have or operators inside. This meant that they were used twice and it also caused problems that an and operator binds stronger than an or operator.

Example:

filter: {
    name: ['Milo', '$or:Garfield'],
    color: ['brown', '$or:white'],
}

SQL Query: ... WHERE ( ("__root"."name" = "Milo" OR "__root"."name" = "Garfield" AND "__root"."color" = "brown" OR "__root"."color" = "white") AND ("__root"."name" = "Milo" OR "__root"."name" = "Garfield" AND "__root"."color" = "brown" OR "__root"."color" = "white")

(See: ... OR "__root"."name" = "Garfield" AND "__root"."color" = "brown" OR ...)

Now in my changes the first operator of a filter is checked, so they are not used twice and also filters that starts with an and operators are put in extra brackets, since in the case of a multifilter they contain or operators and otherwise you would have problems again because of the stronger binding of an and operator.

Example:

filter: {
    name: ['Milo', '$or:Garfield'],
    color: ['brown', '$or:white'],
}

SQL Query: WHERE ( ("__root"."name" = "Milo" OR "__root"."name" = "Garfield") AND ("__root"."color" = "brown" OR "__root"."color" = "white") )

[ppetzold]

Good stuff 🚀

LGTM

[ppetzold]

@anddyyyy46 can you run npm run format and commit? ci is failing

[ppetzold]

🎉 This PR is included in version 9.1.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀