1.7.0 (2022-11-07)
- audits/server: Server may accept other content-type encodings (42c26f7)
- handler: Headers can be native to fetch (d459991)
- handler: Supply context to schema option and improve typings (01c45d8)
- use: Built-in handlers for some environments and frameworks (#13) (750e600)
1.6.1 (2022-09-12)
- server: Accepting application/json SHOULD use status code 200 (9622ea0)
- server: Adjust audits following the spec (2b21b08)
- server: Audits requires 4xx shouldnt consider 5xx (59c51fa)
- server: Audits respect legacy watershed (050c7ba)
- server: Audits safely handle unparsable JSON in response body (f8098b6)
1.6.0 (2022-09-01)
- server: Data entry audits when accepting application/graphql-response+json (fe6f60d)
1.5.0 (2022-08-30)
1.4.0 (2022-08-16)
- handler: JSON body must be an object (f500fa7)
- handler: Request's
body
field may be a parser function (268a4bf)
1.3.0 (2022-08-16)
- Change GraphQL acceptable media type
application/graphql+json
toapplication/graphql-response+json
(d86318a)
1.2.0 (2022-08-12)
- handler:
onSubscribe
can return readonlyGraphQLError
s (5ce6841) - handler: Allow empty query string parameter (necessary for persisted operations) (4eed1d5)
- handler: Don't validate if
onSubscribe
returns execution arguments (17c8007) - handler: Respond with error if GraphQL execution result is iterable (d1ffdf7)
- handler:
onSubscribe
can return anExecutionResult
for immediate result response (0dcaf89) - handler: Expose
getAcceptableMediaType
andmakeResponse
for increased modularity (ae8ea29) - handler: Request may contain a context value (3a593f8)
- handler: Detect non-string query parameter before parsing (4bc71ee)
1.1.0 (2022-08-05)
isResponse
correctly asserts even if body is null (102de6d)- Different types for request and response headers (9e91141)
- handler:
context
option can return a response (86c28d1) - handler: Match status text with status code (f07454d)
- handler: More details about parse error (3306cae)