Details

    • Changelog:
      Hide
      It is now possible to access nested models inside a model through wonderland. Therefore, you need to define the property names in this way:
      Imagine you have a model which has a property of the name 'nested' and this property is itself a model which has two properties, namely 'value1' and 'value2'. You can now access these properties in wonderland with a property name like this: 'nested.value1' or 'nested.value2'
      Show
      It is now possible to access nested models inside a model through wonderland. Therefore, you need to define the property names in this way: Imagine you have a model which has a property of the name 'nested' and this property is itself a model which has two properties, namely 'value1' and 'value2'. You can now access these properties in wonderland with a property name like this: 'nested.value1' or 'nested.value2'

      Description

      Until now the access to the elements of a model class are rather limited. One thing I have seen in every other transformation solution but not in wonderland is the possibility to use nested field access. Assume we have a model which has a sub model. This sub model has two properties, namely "subId" and "subName" for example. And the model has a property of this sub model type with the name "sub".

      If now a transformation is defined, where this model is transformed, it should be possible to access the sub models properties in this way: sub.subName

        Gliffy Diagrams

        Error rendering 'com.meetme.plugins.jira.gerrit-plugin:gerritreviewsmodule'. Please contact your JIRA administrators.

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Felix Mayerhuber
              Reporter:
              Felix Mayerhuber
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: