extnet
absent: ext-panel's HeaderConfig inner block
Found: Ext.NET 7.0.0-preview4_2020-07-18.
This was actually reproduced with an ext-window component, at the Color Picker > Advanced > Components example, but according to Ext JS documentation on Ext.window.Window.header, the configuration comes from Ext.panel.Panel.header.
In the example, the block would be directly translated as:
<headerconfig>
<items>
<ext-component cls="x-panel-header-title-default-framed" html="Color button ⇨" />
<ext-colorbutton width="15" height="15" bindstring="{color}">
<listeners>
<change fn="onChange" />
</listeners>
</ext-colorbutton>
</items>
</headerconfig>
It seems a working conversion would be:
<header>
<ext-header>
<items>
<ext-component cls="x-panel-header-title-default-framed" html="Color button ⇨" />
<ext-colorbutton width="15" height="15" bindstring="{color}">
<listeners>
<change fn="onChange" />
</listeners>
</ext-colorbutton>
</items>
</ext-header>
</header>
Which looks unnecessarily longer/deeper than Ext.NET 5's.
Ext.NET 5 favors using simpler blocks unless extension is to be supported. For instance <HeaderConfig /> always means an ext:Header, whereas a <Store> will mean a "SingleStoreCollection" where it could take any instance of Ext.Net.AbstractStore.
This means the <HeaderConfig /> in Ext.NET won't accept extension whereas <Store /> would; and that's the reason the double recursion for latter while the former is determined straight away.
In fact, Ext.NET solution's SingleStoreCollection could take more than one store in markup and that would be accepted. When the code is rendered though, an exception would be thrown stating only one store may be within the "collection".
