- πΊπΈUnited States mlncn Minneapolis, MN, USA
Coming over to check if Themable forms wanted to join forces with Twig Template Suggestions. We lean toward pointing to modules like themable forms that do more specific things but it's hard to keep track of multiple modules, such that in 2021 we pushed back on apparent duplicate functionality in π Theme suggestions for (form) fieldsets per form ID Fixed and then this year accepted a merge request that did the same β¨ Forms do not have theme suggestions Fixed . For people not maintaining and contributing to either module, it is presumably even harder to keep track! Especially if the energy to maintain separate modules is lacking, maybe we should merge as was suggested in #3057385: Merge themable_forms into twigsuggest β / π± Merge into Twig Template Suggester Active .
So i think either we document each other and themable forms gets a Drupal 10 release and i'll revert this commit, or a maintainer or two comes over and we join forces?
- Status changed to Needs review
almost 2 years ago 8:59am 31 January 2023 - πΊπΈUnited States mlncn Minneapolis, MN, USA
Wow just realizing that what we just committed does not overlap with themable forms after all.
We already do document Themable forms on the Twig suggest β module page:
For form elements per element type and form ID, use Themable forms β .
Perhaps Themable forms could add this line to its project page:
For form templates per form ID and many non-form template suggestions, see Twig Template Suggester β
.
- πͺπ¨Ecuador jwilson3
Updated issue summary with suggested documentation changes
- π©π°Denmark ressa Copenhagen
Thanks @jwilson3 for your efforts with comparing the Twig template solutions available, it was really helpful for me to get an overview.
I have added a new "Get more specific Twig suggestions" section on the Working With Twig Templates β documentation page.
Feel free to expand, edit it, or otherwise improve it. My aim is to guide people to that page, if they search for "drupal twig template suggestions".