FLUID-5357: Allow transformation rules to default to inputPath of "" if neither input nor inputPath are specified

Metadata

Source
FLUID-5357
Type
Improvement
Priority
Major
Status
Open
Resolution
N/A
Assignee
Kasper Galschiot Markus
Reporter
Antranig Basman
Created
2014-05-02T15:19:42.766-0400
Updated
2021-07-29T01:34:26.643-0400
Versions
N/A
Fixed Versions
  1. 5.0
Component
  1. Model Transformation System

Description

This appeared in some work on the metadata component discussed on IRC at https://botbot.me/freenode/fluid-work/msg/14144056/ (2/5/14 at 1.07pm).
It seems as if it would be helpful if there is no other specification of an input, to assume that inputPath: "" was meant.
This would be very simple to implement but as usual with MT we need to think hard to ensure that this doesn't have any unexpected and unpleasant consequences in some scenario.

Comments

  • Antranig Basman commented 2017-09-28T07:31:24.347-0400

    This should be implemented at least to the extent that the valueMapper example pasted on FLUID-6179 can function without the additional path specification - note that for a relay specification with valueMapper we need to write the following:

    singleTransform: {
            type: "fluid.transforms.valueMapper",
            defaultInputPath: "", // required due to FLUID-6179 not yet resolved
            match: [{
                inputValue: null,
                outputValue: "{that}.options.icons.keyedOut"
            }],
            noMatch: "{that}.options.icons.keyedIn"
        }