Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
1.5
-
None
Description
When valueMapper is used to transform compound input values, "defaultOutputValue" is not properly handled.
Example:
var rules = { type: "fluid.transforms.valueMapper", inputPath: "", defaultOutputValue: false, options: [{ inputValue: { "isTooltipOpen": true, "isDialogOpen": true }, outputValue: true, }] };
In cases that the input value is NOT
{ "isTooltipOpen": true, "isDialogOpen": true }
We expect the output value is false.
However, what happens is, the output value is always true regardless of value combinations of "isTooltipOpen" + "isDialogOpen".
Attachments
Issue Links
- relates to
-
FLUID-5473 defaultOutputValue in valueMapper isn't applied in case of no match/ambiguous match
-
- Closed
-