-
Notifications
You must be signed in to change notification settings - Fork 121
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
new fields added to post model #97
Comments
@SergeyRe I'm not sure I understand what question you are asking. If you want to add new fields you should be able to do that. Simply add the new field in Contentful, add the corresponding query on your site and it should be inferred and part of your GraphQL response. If it is not showing up you may need to regenerate the graphql snapshot since this starter uses |
Thanks for response |
Gotcha. No worries. It's fine to remove that plugin. I only included it as a way to "lock down" the expected fields so that even if the content didn't exist in Contentful the site would still be able to build. I am going to close out this ticket. Best of luck to you. |
Hi Ryan and thanks for the useful template. We are using it to help those effected by the massive explosion in downtown Beruit. I ran into the exact problem above and, not being familiar with the snapshot plugin, spent quite a bit of time debugging before I saw this.You might consider adding a note about this in the readme. |
Thanks for the feedback @DannyBoyNYC. I will definitely look at adding something to the readme to make it more clear. If you have any other questions or suggestions feel free to let me know. And of course good luck on your project for a good cause. I’d love to see the final result. Send me a tweet or something when it launches https://mobile.twitter.com/ryanwiemer |
are not sown at GraphiQL schema.
Situation closed to described here
possible bug? new contentful model field does not show up in graphql response
Meanwhile empty gatsby project with contentful plugin directed to the same space reproduce correct
The text was updated successfully, but these errors were encountered: