- Issue created by @larowlan
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
π Maintain a per-component set of prop expressions/sources Active landed.
- π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
Can I suggest something other than propSources - we'll likely want to ship jsonSchema for block components - and currently this sits under field_data.
Or if we rename it to propSources, can we move the schema elsewhere?
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
Or if we rename it to propSources, can we move the schema elsewhere?
I think this makes more sense?
Block
Components
useexport interface SimpleComponent {
on the client side, and they don't have this either. And π [PP-1] Implement client-side validation of block settings Active will want that kind of information for
Block
s.So β¦ expanding
SimpleComponent
with schema information seems sensible to me? π