Closed dbvisel closed 3 years ago
(and I think this also causes Gatsby Cloud failures, though the logs there don't show a lot of info.)
but my impulse was security-minded, and I thought the less that Gatsby knew the better.
💯
I'll see if I can patch this and make Gatsby helper a little bit more aware of the schema when queried about updated elements.
Okay, just fixed this for the next release.
To get the fix early, change your craftcms/gatsby-helper
requirement in composer.json to:
"require": {
"craftcms/gatsby-helper": "dev-develop#01cae0091109da99668128235898d91b9e46b11c as 1.0.0",
"...": "..."
}
Then run composer update
.
I am getting same problem when i changed the files, if we do redeploy and clear cache from netlify it works fine
Description
Hi! I added a new user in my Craft install. My GraphQL schema does not include any users, as the front end doesn't deal with them right now. But this makes the build fail on Netlify:
If I clear the cache on Netlify and redeploy, it's fine. And I suspect that I could make this go away by adding the users to my Gatsby schema – but my impulse was security-minded, and I thought the less that Gatsby knew the better. Is this the way it should behave?
Thanks!