Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Formal schema for blocks? #923

Open
tiberiuichim opened this issue Apr 24, 2020 · 0 comments
Open

Formal schema for blocks? #923

tiberiuichim opened this issue Apr 24, 2020 · 0 comments

Comments

@tiberiuichim
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant