SameeraM,
Do we have any reason to design following section to have 3 nested "name"
properties?
/Ruchira
[1]
name: {
name: {
name: 'name',
label: 'Name'
},
updatable: false,
validation: function() {}
}
On Wed, Jul 15, 2015 at 2:22 PM, Mariangela Hills <mariang...@wso2.com>
wrote:
> Hi team,
>
> Can you please clarify the following doubts:
>
> 1) How come the field "name" appears in three consecutive nested levels in
> the default
> <ES_HOME>/repository/deployment/server/jaggeryapps/publisher/extensions/assets/default/asset.js
> [1] file?
>
> 2) In an offline chat, you mentioned that the properties returned by the
> asset.configure callback function were as follows: name, label, type,
> readonly, hidden, updatable. As the field "label" appears at a different
> level when compared to the other fields, is it correct to have "label" too
> as a property that is returned by the asset.configure callback method? If
> 'label' is actually a property that is returned, shouldn't it be defined at
> the same level as the other properties that are returned?
>
>
> [1]
> asset.configure = function() {
> return {
> table: {
> overview: {
> fields: {
> provider: {
> auto: true
> },
> name: {
> name: {
> name: 'name',
> label: 'Name'
> },
> updatable: false,
> validation: function() {}
> },
> version: {
> name: {
> label: 'Version'
> }
> },
> createdtime: {
> hidden: true
> }
> }
> },
>
>
>
>
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
--
*Ruchira Wageesha**Technical Lead*
*WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>*
*email: ruch...@wso2.com <ruch...@wso2.com>, blog:
ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>,
mobile: +94 77 5493444*
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
