Skip to content

Releases: contra/graphql-helix

[email protected]

09 Jul 00:23
f8e9b1a
Compare
Choose a tag to compare

Minor Changes

  • 4d9ec82: Include extensions within the ExecutionContext.
  • 4d9ec82: Include operationName within the ExecutionContext.

[email protected]

08 Mar 14:38
1bbc714
Compare
Choose a tag to compare

Minor Changes

  • baf0b15: Enable to configure allowed HTTP methods for subscriptions.

[email protected]

16 Dec 10:39
3a1c91d
Compare
Choose a tag to compare

Minor Changes

  • f07a403: Adjust the handling of the accept header.

    • Clients accepting the application/graphql+json header (via the accept header) will receive responses that use Content-Type: application/graphql+json over application/json (which is only for supporting legacy clients).
      Clients that do not specify any accept headers will still receive content-type: application/json. This is not considered a breaking change as clients accepting the application/graphql+json header should also be able to process it.
      Note: When using the application/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 a PushResponse instead of a MultipartResponse. Previously helix would send a MultipartResponse if the accept header was not a strict equal to accept: 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.

[email protected]

25 Nov 18:57
42c640e
Compare
Choose a tag to compare

Patch Changes

  • d6071a1: Set content-length header on sendResponseResult

[email protected]

19 Nov 14:33
b6dc4a5
Compare
Choose a tag to compare

Patch Changes

  • ea28821: fix missing context in subscribe function

[email protected]

18 Nov 22:07
9e55fd8
Compare
Choose a tag to compare

Patch Changes

  • b6eff48: Handle errors thrown by subscribe handlers.

    Previously any error raised with a subscribe handler on the Subscription root type was not handled and forwarded to formatPayload, which could potentially lead to error message leaking to clients.

[email protected]

17 Nov 08:01
95c190d
Compare
Choose a tag to compare

Minor Changes

  • d50e833: graphiql: allow to store headers in localStorage (false by default)

[email protected]

04 Nov 11:06
e38b73a
Compare
Choose a tag to compare

Patch Changes

  • a52d40b: fix(processRequest): pass context as contextValue correctly

[email protected]

03 Nov 15:29
c74d31d
Compare
Choose a tag to compare

Minor Changes

  • c8750f3: Added support for GraphQL v16
  • 1ada48e: feat: W3C Response handlers

Patch Changes

  • c8750f3: fix broken multi part response and SSE response fetching in GraphiQL

[email protected]

24 Oct 11:02
56ea0e4
Compare
Choose a tag to compare

Patch Changes

  • f4399bb: terminate SSE HTTP connection after stream ended emitting values
  • f4399bb: fix broken multi part response and SSE response fetching in GraphiQL