I noticed that dato uses a json-schema definition for validating the structure of your own API.
I also love the ERD export of the content model.
I think a valuable feature would be to expose a json-schema definition for our sites’ data models.
reasoning: we’re investigating better ways to enforce data integrity within our sites. to do this we intend to define our content models with json-schema so that we can validate the data is being returned in the proper shape. we also intend to implement a way of syncing changes to the schema back up to Dato so that our engineers can maintain the content model in code (not just through the GUI).
it seems like you’re already keen on json-schema and it’s benefits, it would be great if that could trickle down to our sites’ content models as well
My use case is for using gatsby themes. I want to be able to auto populate datocms models to match my themes so I can get up and running quickly. Looking forward to this
This sounds awesome. I’m excited to use DatoCMS as the Headless CMS solution for a variety of projects and it would make things so easy if we could clone (or export and reimport) the content models we have established to set up new projects.
+1.
Would love the feature. Sometimes I need to change the schema dramatically. I’m a bit afraid doing so without knowing if I mess up I can revert back easily.
This feature would be great and extremely beneficial for Language Servers and text editors. Considering Schemas have been widely adopted in text editors if Dato was to provide a schema export of projects I could leverage them with an LSP implementation and provide intellisense features like completions, diagnostics and hovers in text editors that support the protocol.
Hi @mat_jack1 . Any news on this feature, we would need it as well. More and more projects migrating to DatoCMS and this would be useful to move certain common models from project to project.
