FLUID-6179: deprecate all top-level defaultXxxx properties in model transformations

Metadata

Source
FLUID-6179
Type
Task
Priority
Major
Status
Open
Resolution
N/A
Assignee
N/A
Reporter
Justin Obara
Created
2017-08-03T14:19:24.094-0400
Updated
2017-09-28T07:36:05.184-0400
Versions
N/A
Fixed Versions
N/A
Component
  1. Model Transformation System

Description

We should deprecate all top-level defaultXxxx properties in favour of implementing them as xxxx. For example changing defaultInput to input.

This issue was originally noticed while updating the valueMapper for FLUID-6174.

See: https://github.com/fluid-project/infusion/pull/838#discussion_r131189199

Comments

  • Antranig Basman commented 2017-09-28T07:32:30.056-0400

    Hopefully a side-effect of resolving this issue would enable the valueMapper to be used as a singleTransform in a relay rule without spuriously needing the a "path" element set - as in

    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"
        }

    see https://codepen.io/Bosmon/pen/NajXZZ?editors=1111