Match op doc

[Mat]

Does this in the match operator doc actually make sense?

First, it is referred to as a "<flag list>" but the table says "suffix" which is also the term used in other docs. Would it better to change <flag list> into <suffix list>?

Second... does it make sense to talk about a list of suffixs at all? The two options are "casesensitive" and "caseinsensitive", i.e mutually exclusive. Maybe the match op is set up to handle a larger number of suffixes?

<:-)

[PMario]

Hi Mat,
Yes it does make sense.

The basic filter build block looks like this.

[operator:suffix[<operand>]] eg: [field:author[pmario]]

In this case the suffix is the field name author.

Core internally there is the possibility, that operators can have more "suffixes", that are separated by "colons" like:

[operator:suffix-0:suffix-1:suffix-2[<operand>]] ... which is only used for the "search operator" atm. So you are right, there IS a suffix-list, BUT it is different to the flag-list

In case of the match operator "suffix-0" is a <flag-list> .. because the js code treats the first suffix as a flag-list. Those flags are separated by "commas"

So 1 suffix can contain a "flag-list".

A "basic form" for search could be written like:

[search:suffix-0:suffix-1[operand]]

or more precise like:

[search:<field list>:<flag list>[<operand>]]

hope that helps

mario

[Mat]

Great reply - thank you Mario!

<:-)