graphql-spec
graphql-spec copied to clipboard
Fix normative requirement around `errors` property
Whilst reviewing #966 I spotted this; I don't believe this is a breaking change since it can be derived from:
The
errorsentry in the response is a non-empty list of errors, where each error is a map.
So if no errors occur, then the "errors" key must not (rather than "should not") be present, since it's forbidden to be an empty list, it contains errors, and no errors occurred.
Deploy Preview for graphql-spec-draft ready!
| Name | Link |
|---|---|
| Latest commit | 7f541ddf1a58dd2fe915028c3ffa759426107ab2 |
| Latest deploy log | https://app.netlify.com/sites/graphql-spec-draft/deploys/62b2c3763891f50009a2a9ac |
| Deploy Preview | https://deploy-preview-967--graphql-spec-draft.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Changes were incorporated into #966