- Notifications
You must be signed in to change notification settings - Fork1.5k
docs: add guide on graphql-http errors#2006
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
@sarahxsanders is attempting to deploy a commit to theThe GraphQL Foundation Team onVercel. A member of the Team first needs toauthorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This is really good general reference that should be applicable to any server implementing GraphQL-over-HTTP (not just the reference implementation).
One concern is it does not incorporate theapplication/graphql-response+json
media type. Since the spec is currently a draft I wouldn't normally be too concerned, except we do link to the spec so we should recommend its recommendations.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
vercelbot commentedJun 7, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
The latest updates on your projects. Learn more aboutVercel for Git ↗︎
|
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
added a section about understanding response formats, I hope that addresses this better! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Are we sure about the 415 and 422? The spec itself does not recommend them, it's up to the implementor to choose using it and follow HTTP conventions.
@enisdenjo I removed those sections and added a section w/ a disclaimer, let me know if this addresses that! |
It's looking good now, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Excellent!
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
fb6c6ea
intographql:sourceUh oh!
There was an error while loading.Please reload this page.
Description
graphql-http
errors (just some common ones) and how to debug themFeel free to suggest additional common errors if there are any that might be important to highlight here!