graphql-over-http

graphql-over-http copied to clipboard

Detail HTTP status codes to use for various error conditions

1

We should embrace HTTP semantics as much as possible. Previously I over-specified the status codes to make it seem like 400 should be used for everything when actually you should...

benjie

Use 294 as the partial status code

11

See changes for explanation. Note: this will need testing before we can merge it.

benjie

Should we use/encourage HTTP 422 for validation failures?

1

https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/422 https://github.com/graphql/graphql.github.io/pull/2006/files (Specifically for when the syntax is valid (parse succeeds) but validation fails.)

benjie

[This section](https://graphql.github.io/graphql-over-http/draft/#sel-DALLEVHAAEXBAAl8O) notes: > All other property names are reserved for future expansion; if implementors need to add additional information to a request they MUST do so via other means,...

benjie

Consider simplifying the specification?

7

There has been a lot of discussion lately about how to handle the `Accept` header and response `Content-Type`. 2 recent examples: * https://github.com/graphql/graphql-over-http/pull/322 * https://github.com/graphql/graphql-over-http/pull/327 The current draft of the...

martinbonnin

Fix typos

1

Found via `codespell -L qeury,youre`

kianmeng