Warn if context values passed to createPage are different types than others or empty #4360
Comments
yeah, right now have this issue, trying to fix, but without result :( |
i encounter this issue and found out it is because i didnot write slug in graphql query in the create page function in my gatsby node file |
Hi @KyleAMathews wanted to know if there's any update on this. I'm using a starter for dato, my request in When i try EDIT: So, not so long after posting this i found that the problem came from overriding what |
@Jonqth thanks so much for that last edit. Finally fixed this issue after hours of hunting..! |
Old issues will be closed after 30 days of inactivity. This issue has been quiet for 20 days and is being marked as stale. Reply here or add the label "not stale" to keep this issue open! |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m Thanks again for being part of the Gatsby community! |
I have run into this error today - when creating pages from a folder of Any reason this should be the case? It's not a big deal, but I'd prefer to have the component in my pages folder since it's creating pages. All pages are created as expected, I just get this error. |
I have run into this error when migrating from v1 to v2, the context values passed to createPage are same types and not null. Anyone have same problems? |
@tianzhich I was able to fix the problem after moving my post to |
I solved in #15977 cause the difference between StaticQuery and page query. Maybe it could help someone. |
Someone creating pages could run into a mysterious GraphQL error if any of the pages context has missing information:
This is hard for someone new to Gatsby to debug. We should check against this and warn.
The text was updated successfully, but these errors were encountered: