Releases: contra/graphql-helix
Releases · contra/graphql-helix
[email protected]
[email protected]
Minor Changes
- baf0b15: Enable to configure allowed HTTP methods for subscriptions.
[email protected]
Minor Changes
-
f07a403: Adjust the handling of the
accept
header.- Clients accepting the
application/graphql+json
header (via theaccept
header) will receive responses that useContent-Type: application/graphql+json
overapplication/json
(which is only for supporting legacy clients).
Clients that do not specify anyaccept
headers will still receivecontent-type: application/json
. This is not considered a breaking change as clients accepting theapplication/graphql+json
header should also be able to process it.
Note: When using theapplication/graphql+json
content-type header you need to configure your HTTP server/framework to parse this content-type as JSON. - GET
text/event-stream
requests will now ALWAYS return aPushResponse
instead of aMultipartResponse
. Previously helix would send aMultipartResponse
if the accept header was not a strict equal toaccept: text/event-stream
. - POST requests that try to execute Subscription operations will now receive an error and 405 status code. This is not considered a breaking change as SSE is not doable over POST by the specification and was never officially supported.
- Clients accepting the
[email protected]
Patch Changes
- d6071a1: Set content-length header on sendResponseResult
[email protected]
Patch Changes
- ea28821: fix missing context in subscribe function
[email protected]
Patch Changes
-
b6eff48: Handle errors thrown by subscribe handlers.
Previously any error raised with a
subscribe
handler on theSubscription
root type was not handled and forwarded toformatPayload
, which could potentially lead to error message leaking to clients.
[email protected]
Minor Changes
- d50e833: graphiql: allow to store headers in localStorage (false by default)
[email protected]
Patch Changes
- a52d40b: fix(processRequest): pass context as contextValue correctly