You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Pierre Smits (JIRA)" <ji...@apache.org> on 2016/12/10 09:43:59 UTC
[jira] [Updated] (OFBIZ-9141) Refactor 'default-map-name' and
'list-name' into one mapping definition for form widgets.
[ https://issues.apache.org/jira/browse/OFBIZ-9141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Smits updated OFBIZ-9141:
--------------------------------
Description:
Currently we have:
* 'default-map-name', which can applied to form definitions of type='single'
* 'list-name', which can be applied to form definitions of type='list' and type='multi' and to grid definitions
They both mean the same, and it is the parent definition that defines how the mapped data is rendered.
Refactoring into one definition reduces the footprint, and removes ambiguity.
was:
Currently we have:
* 'default-map-name', which can applied to form definitions of type='single'
* 'list-name', which can be applied to form definitions of type='list' and type="multi and to grid definitions
They both mean the same, and it is the parent definition that defines how the mapped data is rendered.
Refactoring into one definition reduces the footprint, and removes ambiguity.
> Refactor 'default-map-name' and 'list-name' into one mapping definition for form widgets.
> -----------------------------------------------------------------------------------------
>
> Key: OFBIZ-9141
> URL: https://issues.apache.org/jira/browse/OFBIZ-9141
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS, framework
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Labels: refactoring, widget
>
> Currently we have:
> * 'default-map-name', which can applied to form definitions of type='single'
> * 'list-name', which can be applied to form definitions of type='list' and type='multi' and to grid definitions
> They both mean the same, and it is the parent definition that defines how the mapped data is rendered.
> Refactoring into one definition reduces the footprint, and removes ambiguity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)