GraphQL query failure
See original GitHub issueHey Dustin!
First off, wanted to thank you for taking the time to write your blog post on getting a Gatsby blog setup. It was helpful to have some sort of path to creating something working.
Got a question for you though:
query BlogPostByPath($path: String!) {
...
}
When I put this query inside the graphql debugger, it was returning an error for me because it couldn’t find $path. However, when I removed the !
it worked.
query BlogPostByPath($path: String) {
...
}
Could you explain why there is a !
there?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Error handling - Apollo GraphQL Docs
A client sent the hash of a query string to execute via automatic persisted queries, but the server has disabled APQ. OPERATION_RESOLUTION_FAILURE. The...
Read more >A Guide to GraphQL Errors
GraphQL errors encode exceptional scenarios - like a service being down or some other internal failure. Errors which are part of the API ......
Read more >Top GraphQL Errors and How to fix them
GraphQL is strongly typed and it performs validation of all queries before executing them. It can reject a query if it is invalid...
Read more >GraphQL error handling to the max with Typescript, codegen ...
A GraphQL API will always return a 200 OK Status Code, even in case of error. You'll get a 5xx error in case...
Read more >Error Handling in GraphQL - DEV Community
GraphQL servers are able to handle errors by default, both for syntax and validations errors. But often this is not sufficient for more ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@DSchau Ah. I think I see what happened. You provided a Query Variable in the debugger. I didn’t even see that section when I was using the debugger. I just assumed that it would actually query the file system instead of depending on the variable.
Thanks for the response!
No problem!