Hi
In order to overcome limitation described here without reverting to Datasource model, I tried using ComponentGenerationStrategy as described in the documentation.
The strategy code is not called by the platform at all.
Sample project attached.
compgen.zip (82.0 KB)
Hi,
Thank you for the demo project.
In the customer-edit.xml a specific component (textField) is defined for the address attribute:
<textField id="addressField" property="address"/>
As the result, a loader has no need to use a component generator as it certainly knows that a text field must be created.
If you change textField to field then a loader will use component generators.
<field id="addressField" property="address"/>
Gleb
And it works great, thanks @gorelov !
That could be interesting to mention in the documentation page. I am a long time user of 6.10 and with 7.x big changes, I got back to books 