A common challenge one would face when using any CMS is the constant back and forth between developer and content teams. Be it planning and updating content structures in the backend or rearranging content on the frontend of an application, making changes almost always means additional work for both teams. It gets even harder when there is uncertainty around the content structure, how often the content will be updated, and what it will look like. Strapi has an interesting way of making this process more efficient and it comes in the form of a feature called Dynamic Zones.
resulting in a Cannot read property 'types' of undefined error: introspectionResultData.__schema.types.forEach(function (type) {
And that makes sense, because there’s no __schema in my fragmentTypes.json