V5.4.0 prerelease - Clearifications about MVVs using with various operators

Multi-valued variables clarification: do filter operators each have to be individually updated in order to support MVVs?

The MVV docs say “Certain filter operators can accept multi-valued parameters: function Operator, title Operator”. Does that mean that these are the only operators that will understand MVVs, and everything else treats them as single values?

(If so, that severely limits their possibilities…)

Most operators operate on input and don’t make much use of parameters. Only parameters need special support for handling MVV. Which operators did you have in mind which you want to pass MVV as parameter?

Aha. Well, if the parameters are what need to be manually updated, then that explains why the operators I tried weren’t working, because they were all in the format of operator(var)! Doing some quick testing now shows that yes, ones that don’t require parameters (like uppercase[]) are working as I expect them to.

(My initial test was a nested jsondexes & jsonget combo, which I thought should work fine because Jeremy had used jsonget in examples for his initial MVV presentation. Didn’t work, a jsonget(var1),(var2),[text] treated them as single values. My “sanity checks” of addsuffix(var) / addprefix(var) failed likewise. Guess I know why now…)