Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Be strict about error paths format #1073

Merged
merged 3 commits into from
Apr 4, 2024
Merged

Be strict about error paths format #1073

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4b8bbdd
Be strict about error paths
martinbonnin Jan 25, 2024
2866095
Update spec/Section 7 -- Response.md
martinbonnin Feb 1, 2024
88d99e5
format
martinbonnin Feb 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions spec/Section 7 -- Response.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,11 +109,11 @@ must contain an entry with the key `path` that details the path of the response
field which experienced the error. This allows clients to identify whether a
`null` result is intentional or caused by a runtime error.

This field should be a list of path segments starting at the root of the
response and ending with the field associated with the error. Path segments that
represent fields should be strings, and path segments that represent list
indices should be 0-indexed integers. If the error happens in an aliased field,
the path to the error should use the aliased name, since it represents a path in
If present, this field must be a list of path segments starting at the root of
the response and ending with the field associated with the error. Path segments
that represent fields must be strings, and path segments that represent list
indices must be 0-indexed integers. If the error happens in an aliased field,
the path to the error must use the aliased name, since it represents a path in
the response, not in the request.

For example, if fetching one of the friends' names fails in the following
Expand Down
Loading