- Issue created by @wim leers
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Is this a duplicate of 📌 Discover cases where is no 1:1 map between field, prop and widget values Active which has lots of child issues already?
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
AFAICT the last step in the issue summary is basically 📌 [PP-2] Redux sync on ALL prop types, not just ones with a single [value] property Postponed , which this then essentially blocks: we FIRST need the shape matching, to make the widget show up at all, and THEN #3463842 can make those widgets work.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
#6: No, AFAICT it's tackling a very different problem space. See 📌 [PP-2] Redux sync on ALL prop types, not just ones with a single [value] property Postponed for my write-up, please confirm my understanding there, because I could totally be wrong here 😅
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
… which led me to re-discover 📌 Provide visibility into field types with different matching SDC prop shapes depending on field storage settings Active .
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Per #3512854-19: Find bug(s) that explain unmatched field type properties → , those 2 new additions do not belong here; they belong under 🌱 [META] 7. Content type templates — aka "default layouts" — clarify the tree+props data model Active instead.
- 🇫🇮Finland lauriii Finland
We don't have support for rendering nodes in XB at 1.0.0 so I think most of this can be moved to later. There's still remaining work but we should probably track that in 🌱 [META] 7. Content type templates — aka "default layouts" — clarify the tree+props data model Active .