fluid.transforms.valueMapper should support a direct input value

Description

Currently the fluid.transforms.valueMapper model transformation only supports input paths. There should be an option to take in an input value directly. In addition to being able to supply the model data directly, it will also allow for supporting nested transformations.

Environment

None

Activity

Show:

Antranig Basman July 30, 2017 at 11:03 PM

Thanks, , this report exposes an interesting blunder in the re-implementation of the valueMapper. As you can see from the draft format listed in that JIRA, the intention was always to support a top-level "input" option but somehow this was never done. This escaped notice since the only major user of the valueMapper is currently the GPII which uses static "big up front documents". I imagine if we had ever dusted off the in-progress work on metadata editing by et al this problem would have come to light earlier. We need to have a brief chat with to confirm that our understanding of the issue is correct.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created July 29, 2017 at 12:57 PM
Updated July 22, 2024 at 2:35 PM
Resolved August 11, 2017 at 2:02 PM