MapValue action now always multiple?
A while ago, the "Map Value" action would only map a single string/number to another one.
However, with commit bffa7cb2, which seems to aim at enabling the mapping for multiple values, this isn't possible any more. Since the input_value
specification is now multiple=true
(see here), the result is always an array. This breaks form processors based on the original implementation ("requires a single value a multiple value is given").
My questions are:
- Was this change introduced on purpose, or was that a side effect that hasn't affected anyone else yet?
- Could I get my old behaviour back by -for example- adding a "return first value" configuration option? Or maybe by splitting this into a "Map Value" and a "Map Values" action?
@jaapjansma Would you have an opinion on this?