Clarification about usage of 404 not found in the `application/graphql-response+json` spec
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- graphql
- Domain
- api
Research direction
The payload names no files, so start in the draft specification text and find the section on HTTP status codes for 4xx responses, then read the three existing comments for any decision already reached. Work here means answering whether a missing resource should return 404 or 200 with data: null, and the result is either a maintainer-agreed answer or a proposed wording change to the spec. Expect to need maintainer input before writing anything.
Written by the indexing model from the issue text.
Description
Hey hey,
Not sure if this is the right place to ask, but hopefully someone can still help us out :)
We are currently implementing application/graphql-response+json, which means we should use standard HTTP status codes. We are, however, having a discussion about how to handle cases where the requested data, such as a user, does not exist.
According to this specification, should we return a 404 status code, or should we return a 200 response with "data": null?
We could not find this scenario in the section with all the 4xx status code examples, which made us wonder.
Thanks in advance 😄
- Dominant language
- JavaScript
- Stars
- 428
- Forks
- 70
- Avg merge
- 11m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from graphql/graphql-over-http
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
graphql/graphql-over-http#415 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
graphql/graphql-over-http#392 · 4 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
graphql/graphql-over-http#242 · 8 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
graphql/graphql-over-http#216 · 15 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
graphql/graphql-over-http#205 · 18 comments ·
All issues in graphql/graphql-over-http
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openlayers/openlayers#17736 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
521xueweihan/HelloGitHub#4326 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Mintplex-Labs/anything-llm#7133 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day