- 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.