[PP-2] Redux sync on ALL prop types, not just ones with a single [value] property

It may be possible to do this within one MR, but if there are prop types that prove challenging I think it is reasonable to make those separate issues.

Indeed, let's find out :)

See my related comment at #3462441-15: Contextual form values need to be integrated with Redux: start with single-property field types → .

I think that for most field types, your remark will end up being true, but not for all. I think we might need some talking to the server for some props … but I will hopefully be wrong 😄

Still, for the ~90% case, I think what you wrote here will be feasible … and obviously would result in a much better UX (no network latency)!

✨ Contextual form values need to be integrated with Redux Active is in! 🥳

Per #3463583-22: Use the `all-props` component for testing form backend + frontend integration → , this is essentially actionable now. 👍

📌 Create a component for testing form backend + frontend integration Active landed weeks ago 👍

@bnjmnm, FYI: this has been added to 🌱 Milestone 0.1.0: Experience Builder Demo Active not to solve all the things, but to address at minimum ✨ Allow components to use textarea in favor of input Needs review — and perhaps also type: boolean (the latter is AFAICT a blocker in 📌 Component props form: map textarea, bool, and select elements to React components Fixed being reported by Utkarsh).

(i.e. make at least those 2 field widgets work, just like 🐛 Prop select lists don't affect the component Fixed made <select> work.)

It makes sense to me to prioritize this issue now, so that @bnjmnm can convert it to a meta issue where he outlines his plan for scaling this to all Drupal core field widgets.

FYI, per 🐛 [PP-1] Can't toggle boolean prop back to true after changing to false Postponed , @kristen pol created these related issues, which I suspect ought to be child issues of this one:

• 🐛 [PP-1] Can't toggle boolean prop back to true after changing to false Postponed
• 🐛 Redux support for ImageWidget: `[image] String value found, but an object is required` Postponed

Another issue that is closely related to this: 🐛 Redux support for ImageWidget: `[image] String value found, but an object is required` Postponed .

I think the solution that 📌 Media Library integration (includes introducing a new main content renderer/`_wrapper_format`) Fixed introduced with data-media-file is not scalable/sustainable. But I do think there also is an opportunity to solve this generically.

See https://git.drupalcode.org/issue/experience_builder-3463842/-/tree/34638... for an outline (explained in 3 commits) of what I have in mind 🤓 (Although that surely won't work for real-time updates, only for AJAX updates, which is the case for complex widgets like image, media library, etc.)

Although they are supposed to be solved in this issue, the image and textarea issues were solved in:

🐛 XBEndpointRenderer & processResponseAssets() do not support `ajaxPageState` ⇒ duplicate CSS/JS loading Fixed

so I'm using that branch for now so XB is more usable for dev+testing.

bnjmnm → changed the visibility of the branch 3463842-redux-sync-all-kindsa-props to hidden.

📌 Redux Sync all single-value types in the SDC test all props form Fixed is in 👍

What's the next step, @bnjmnm? :)

Per #3467870-16: Support `{type: array, …}` prop shapes → , multi-value field widgets are coming (to support type: array), and that will inevitably impact the infrastructure that enables Redux-powered live updates.

As I described in #18 over there, having that issue in would allow this issue to design a more complete solution.

So: consider this an FYI, @bnjmnm 😊

📌 Move clientside assumptions about prop form data shape into a series of prop specific transforms Active laid important foundations to push this forward, and so does 📌 Maintain a per-component set of prop expressions/sources Active .

This is not just on @bnjmnm anymore, fortunately 😊