Spin-off from: #1263478: Identify pieces of Drupal that could be replaced by Symfony code →
Converting the form system seems to make sense for several reasons:
1) less code to maintain,
2) one less drupalism,
3) decreased memory footprint [based on some basic comparisons]
4) lazy loading due to class loader
- Symfony form component documentation - http://symfony.com/doc/current/book/forms.html
- Currently, the FAPI and render API are similiar, but not entirely the same. In order to use symfony2 form component the render API will need class components as well that will probably stay Drupal specific and simply work together with form API. Otherwise I suppose we would have to use templates for everything, unless there is some other existing mechanism to mimic the render API in symfony.
- Determine what parts of the render API need to be mimicked as classes
- Evaluate wrapping Symfony validation and submit handlers with Drupal hooks vs using directly
- Work on a prototype
Postponed: needs info
11.0 🔥
forms system
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
So wonder if this is still needed or if we should close out?
If no follow up could be eligible to be closed in 3 months
Thanks all!
I think it needs a more generic follow-up not focused only on Symfony Form component. Something like "Modernize Drupal Form API".
There is #1843798: [meta] Refactor Render API to be OO → already.