Looks like we can't reproduce the issue or there's a problem in the test case provided.
NestedList should apply "defaults" configuration to child Lists in getListConfig
The title says it all, NestedList today does not allow much flexibility in customizing child lists because of hard-coded xtype and tpl in getListConfig method.
It should be more flexible and apply "defaults" configuration first and then use an applyIf to add important things like xtype, itemTpl etc. to ensure that the "defaults" config option takes precendence if specified.
The defaults Object is applied to the child lists but not within getListConfig... when the item is being added to the parent
Hi Mitchell, that is exactly my point.
getListConfig today hard-codes the xtype for a card in the nested list. So if I want to customize a card, and I create a List derived base class and specify its xtype in NestedList's defaults, the same is NOT alllied because of hard-coded xtype in getListConfig.
I had to sub-class NestedList, override getListConfig and then specify the xtype for my new List derived component to enable it to be used as a Card.
But if you set the defaults object on the nestedlist... the children when added get the defaults. This is done when adding a component, not in getListConfig so this works 100%
You still do not get what I am trying to say Mitchell.
getListconfig has a hard-coded xtype for 'list'. If Touch does not hardcode it but specify it in config as:
That was we can easily override an individual card in the NestedList to be a List derived custom class.