FLUID-4727: The valueMapper transfomer should not throw an error when an inputPath doesn't match and there is no default value

Metadata

Source
FLUID-4727
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Kasper Galschiot Markus
Reporter
Colin Clark
Created
2012-07-06T17:06:33.575-0400
Updated
2015-06-11T05:36:01.844-0400
Versions
N/A
Fixed Versions
N/A
Component
  1. Framework

Description

At the moment, fluid.model.transform.valueMapper() will throw an error if:

1. the specified inputPath resolves to undefined in the source model
2. there is no defaultInputValue specified

In the GPII, we have found that it can legitimately be the case that a path simply isn't available in the source model and there's no relevant default value (or it would be extremely tedious to specify a default value of "undefined" for each rule).

valueMapper() should be modified to simply do nothing in the above case.

Comments