Skip to content

CHANGELOG.md

Latest commit

 

History

History
517 lines (328 loc) · 24.3 KB

CHANGELOG.md

File metadata and controls

517 lines (328 loc) · 24.3 KB

@graphql-tools/executor-graphql-ws

3.1.5

Patch Changes

3.1.4

Patch Changes

3.1.3

Patch Changes

3.1.2

Patch Changes

3.1.1

Patch Changes

3.1.0

Minor Changes

  • #1518 a9ec688 Thanks @enisdenjo! - Improve isomorphic WS, and drop isomorphic-ws, for accurate usage in all platforms that natively support WebSockets

Patch Changes

3.0.1

Patch Changes

  • Updated dependencies [b0e5568]:
    • @graphql-tools/executor-common@1.0.1

3.0.0

Major Changes

Patch Changes

  • Updated dependencies [46d2661]:
    • @graphql-tools/executor-common@1.0.0

2.0.7

Patch Changes

2.0.6

Patch Changes

2.0.5

Patch Changes

  • #862 278618a Thanks @ardatan! - Use signal.addEventListener instead of leaking registerAbortSignalListener helper

2.0.4

Patch Changes

2.0.3

Patch Changes

  • Updated dependencies [a289faa]:
    • @graphql-tools/executor-common@0.0.3

2.0.2

Patch Changes

2.0.1

Patch Changes

  • #591 7d42160 Thanks @ardatan! - Fix the regression preventing users from passing custom lazy and lazyCloseTimeout options

2.0.0

Major Changes

  • #481 0b13cb4 Thanks @enisdenjo! - Executor options don't exist graphql-ws dependency options

    Removing the dependency on the types. Some options are still exposed, but if you want to further customise the graphql-ws client, you should pass your own instance of the client instead.

    import { buildGraphQLWSExecutor } from '@graphql-tools/executor-graphql-ws';
import { createClient } from 'graphql-ws';
import { options } from './my-graphql-ws-client-options';

const executor = buildGraphQLWSExecutor(
  createClient({
    url: 'ws://localhost:4000/graphql',
    ...options,
  }),
);

  • #481 0b13cb4 Thanks @enisdenjo! - Upgrade graphql-ws to v6

    If you have a custom graphql-ws configuration when building the executor with buildGraphQLWSExecutor, you will have to migrate the graphql-ws side to v6. Please consult the changelog of graphql-ws.

Minor Changes

Patch Changes

1.3.7

Patch Changes

  • #381 55eb1b4 Thanks @ardatan! - dependencies updates:

  • #381 55eb1b4 Thanks @ardatan! - This is a bugfix with some internal changes, no user action is needed. This bugfix and improvement is done to improve the stability of some components of the gateway;

    Like HMAC Upstream Signature plugin, different components of the gateway were using different ways of serializing the execution request. Some of them were ignoring variables if it is empty, some of not, this was causing the signature generation to be different for the same query. For example, it was working as expected in Proxy mode, but not working as expected in Federation Gateway mode.

    With this change, now we have a shared helper to serialize the upstream execution request with a memoized print function for query AST etc to have a consistent serialization so consistent signature generation for HMAC.

    For example instead of using print, you should use defaultPrintFn that memoizes print operation and also used the string version of it parsed before by Envelop/Yoga.

    -import { print } from 'graphql';
-const query = print(parsedQuery);
+import { defaultPrintFn } from '@graphql-tools/executor-common';
+const query = defaultPrintFn(parsedQuery);

    Or instead of creating objects from ExecutionRequest, use serializeExecutionRequest helper.

    -const serializedRequest = {
-  query: print(executionRequest.document),
-  variables: executionRequest.variables,
-  operationName: executionRequest.operationName,
-  extensions: executionRequest.extensions,
-};
+import { serializeExecutionRequest } from '@graphql-tools/executor-common';
+const serializedRequest = serializeExecutionRequest(executionRequest);

  • Updated dependencies [55eb1b4]:

    • @graphql-tools/executor-common@0.0.1

1.3.6

Patch Changes

1.3.5

Patch Changes

1.3.4

Patch Changes

1.3.3

Patch Changes

1.3.2

Patch Changes

  • Updated dependencies [dc5043b]:
    • @graphql-tools/utils@10.5.6

1.3.1

Patch Changes

  • Updated dependencies [cf2ce5e]:
    • @graphql-tools/utils@10.5.5

1.3.0

Minor Changes

1.2.1

Patch Changes

  • #6536 3facde0 Thanks @EmrysMyrddin! - webSocketImpl and lazy options were ignored and overriden by default values. This is no longer the case and it's now possible to change the WebSocket implementation.

1.2.0

Minor Changes

  • #6323 cacf20f Thanks @ardatan! - Implement Symbol.dispose or Symbol.asyncDispose to make `Executor`s `Disposable`

Patch Changes

  • Updated dependencies [cacf20f]:
    • @graphql-tools/utils@10.3.0

1.1.2

Patch Changes

1.1.1

Patch Changes

  • #5666 6269314d Thanks @ThomasMoritz! - changed the order how the configuration is given into the graphql-wsclient and prevent the overwriting of the parameters

1.1.0

Minor Changes

1.0.2

Patch Changes

1.0.1

Patch Changes

1.0.0

Major Changes

Patch Changes

0.0.14

Patch Changes

0.0.13

Patch Changes

0.0.12

Patch Changes

0.0.11

Patch Changes

0.0.10

Patch Changes

  • Updated dependencies [b5c8f640]:
    • @graphql-tools/utils@9.2.1

0.0.9

Patch Changes

0.0.8

Patch Changes

0.0.7

Patch Changes

  • 1c291f33 Thanks @ardatan! - Support regular queries and mutations in WS Executor

0.0.6

Patch Changes

0.0.5

Patch Changes

  • Updated dependencies [904fe770]:
    • @graphql-tools/utils@9.1.3

0.0.4

Patch Changes

  • Updated dependencies [13c24883]:
    • @graphql-tools/utils@9.1.2

0.0.3

Patch Changes

  • Updated dependencies [7411a5e7]:
    • @graphql-tools/utils@9.1.1

0.0.2

Patch Changes

0.0.1

Patch Changes
⚡