Evolve component instance edit form to become simpler: generate a Field Widget directly

📌 Add component instance edit form to contextual panel RTBC must land first.

📌 Add component instance edit form to contextual panel RTBC landed! This can now be worked on. 👍

I'm still very strongly in favor of writing actual react components for each widget with a way for people to swap them in.
We did this in decoupled LB. It's a lot less magic.

I'm still very strongly in favor of writing actual react components for each widget with a way for people to swap them in. […] It's a lot less magic.

There's no question that there's a lot of complexity. AFAIK writing React-based widgets is intended to become possible too, eventually.

For more context, see my detailed response at #3452512-38: Add component instance edit form to contextual panel → .

This blocks 📌 Component props form: map textarea, bool, and select elements to React components Fixed .

Note: it looks like this unveiled a minor but high-impact oversight in semi_coupled.engine: default values for forms are not rendered when using that engine (see screenshots above), but are rendered when using the default engine (reproduce by adding an early return to experience_builder_form_component_props_form_alter()):

🤯

+69,-210 🥳

Yay, the MR is green — only the phpcs CI job is failing, but that's due to 📌 CI: phpcs job failing due to upstream changes in Drupal core: comments must start with capital letter Active .

Looks good

So much better

Updated #3462310-10: Component edit form: make form elements match design → and I see @bnjmnm already started working on ✨ Contextual form values need to be integrated with Redux Active 🚀

Automatically closed - issue fixed for 2 weeks with no activity.