You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It starts to make sense that blocks should have their own schema, similar to the dexterity types schema.
In our projects we've already started using schema for blocks (a similar schema to the one that's serialized by the @types endpoint. For example we have a schema that's being edited through a component derived from Form.jsx.
Having a formal schema for blocks would allow an existing PR to be better implemented. Imagine that, benefiting from that schema, the converter for a block can process the block schema and convert each individual field in that schema. So, instead of trying to find url fields in the block value, the generic resolveuid PR would implement a converter for a block field called "href".
Another benefit, block schema definitions can be saved on the backend. New block types could be created TTW and stored in the backend.
The text was updated successfully, but these errors were encountered:
It starts to make sense that blocks should have their own schema, similar to the dexterity types schema.
In our projects we've already started using schema for blocks (a similar schema to the one that's serialized by the
@types
endpoint. For example we have a schema that's being edited through a component derived from Form.jsx.Having a formal schema for blocks would allow an existing PR to be better implemented. Imagine that, benefiting from that schema, the converter for a block can process the block schema and convert each individual field in that schema. So, instead of trying to find url fields in the block value, the generic resolveuid PR would implement a converter for a block field called "href".
Another benefit, block schema definitions can be saved on the backend. New block types could be created TTW and stored in the backend.
The text was updated successfully, but these errors were encountered: