- Issue created by @bnjmnm
- π§πͺBelgium Wim Leers Ghent π§πͺπͺπΊ
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)!
- π§πͺBelgium Wim Leers Ghent π§πͺπͺπΊ
β¨ Contextual form values need to be integrated with Redux Active is in! π₯³
- π§πͺBelgium Wim Leers Ghent π§πͺπͺπΊ
Per #3463583-22: Use the `all-props` component for testing form backend + frontend integration β , this is essentially actionable now. π
- Status changed to Active
4 days ago 11:14am 4 September 2024 - π§πͺBelgium Wim Leers Ghent π§πͺπͺπΊ
π 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.
- π§πͺBelgium Wim Leers Ghent π§πͺπͺπΊ
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:
- π§πͺBelgium Wim Leers Ghent π§πͺπͺπΊ
Another issue that is closely related to this: π Redux support for ImageWidget: `[image] String value found, but an object is required` Needs work .
I think the solution that π Media Library integration (includes introducing a new main content renderer/`_wrapper_format`) Needs work 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.)