- 🇫🇷France flocondetoile Lyon
I would like to support any content entity type. But...It looks like each entity type provide its twig template (like commerce-product_form.html.twig) with specific class for the main and secondary region.
<div class="layout-product-form clearfix"> <div class="layout-region layout-region-product-main"> {{ form|without('advanced', 'footer', 'actions') }} </div> <div class="layout-region layout-region-product-secondary"> {{ form.advanced }} </div> <div class="layout-region layout-region-product-footer"> <div class="layout-region-product-footer__content"> {{ form.footer }} {{ form.actions }} </div> </div> </div>or for node-edit-form.html.twig by seven / claro theme.
<div class="layout-node-form clearfix"> <div class="layout-region layout-region--node-main"> <div class="layout-region__content"> {{ form|without('advanced', 'footer', 'actions') }} </div> </div> <div class="layout-region layout-region--node-secondary"> <div class="layout-region__content"> {{ form.advanced }} </div> </div> <div class="layout-region layout-region--node-footer"> <div class="layout-region__content"> <div class="divider"></div> {{ form.footer }} {{ form.actions }} </div> </div> </div>Looks like it's not really possible to support any content entity form in a generic way. If someone have an idea, I'm listening.
If not, we could support at least entity type which are requested in the issue queue as patch #7 does.