The form system is currently closely coupled to the Module and Theme system via alters. That's undesireable as it makes it harder to test the core of the form system. It also inhibits our ability to (later), abstract FAPI out entirely. (Whether there is value to doing so or not, there are architectural benefits to the decoupling that would entail.)
Factor the module and theme dependencies out of FormBuilder and into an interstitial "alter" object. That adds a decoupling between FormBuilder and Module/ThemeHandler. The net effect is identical for the 99% use case, but improves the separation of concerns within FAPI.
This is primarily an internal improvement to FAPI and not an API change for anyone except core FAPI developers.
Commit?
None.
No public facing changes; just internal to FAPI.
Closed: outdated
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.