Closed tbrannam closed 3 years ago
Yes, in recent versions, to achieve better loading performance, we had to make changes to how we store information inside the nodes, so yeah, the correct way now to read information is using source.entityPayload
which returns exactly the JSON API response of our CMA with no transformations
Some custom resolvers that we have implemented fail when using
gatsby-source-datocms
version 2.5.0+.The shape of the first argument of the resolver (shown in gatsby-node.js in the examples) receives different shapes of data between these versions.
Note that the CMS Model fields in nested into
entityPayload.attributes
instead of being at the root in prior versionsI've isolated the code into these two sandboxes. They require an update gatsby-config.js with a Dato apiKey.
https://codesandbox.io/s/dato-source-graphql-v241-public-p35io?file=/README.md
https://codesandbox.io/s/dato-source-graphql-v250-public-z4wfs?file=/README.md
Using one of my Dato environments I can make this query using 2.4.1, but fails on 2.5.0 and newer