FLUID-4695: Add the ability to specify transformations in the Model Transformation framework for outputPaths that aren't predetermined

Metadata

Source
FLUID-4695
Type
New Feature
Priority
Critical
Status
Closed
Resolution
Fixed
Assignee
Justin Obara
Reporter
Colin Clark
Created
2012-04-12T13:15:10.447-0400
Updated
2014-04-04T15:22:23.805-0400
Versions
N/A
Fixed Versions
  1. 1.5
Component
  1. Framework

Description

At the moment, Infusion's model transformation framework takes a simple approach to specifying transformation using the following forms:

<output path>: {
expander: {
type: <expander type>,
inputPath: <input path>
<remaining expander options>
}
}

and the shorthand:

<output path>: <input path>

However, for cases where the output path is determined by some aspect of the transformer itself, we need to support a form like this:

{
<output path>: <input path>,
expanders: [
{
expander: {
type: <expander type>,
inputPath: <input path>
outputPath: <output path>
}
}
]
}

Comments

  • Antranig Basman commented 2012-11-26T05:25:45.379-0500

    This facility is now delivered in the Model Transformations system in trunk