On Wed Sep 17 12:53:46 2025 +0000, Rémi Bernon wrote:
Hmm, it still doesn't seem good to have two different ways to express an AND, one supported and one not, when both are supposed to be equivalent. Maybe boolean expressions should be supported first, or maybe we should only support parsing AND (explicit or not) for now, with the joined filters.
Although I guess it's perhaps also how native parses the expressions, though we don't really know, if we assume the filter are a pristine representation of the parsed string. Anyway it's probably fine, we have FIXMEs.