Skip to content

Releases: ardatan/graphql-tools

July 23, 2024

23 Jul 13:15
d46f41b
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Minor Changes

July 23, 2024

23 Jul 11:07
ad8d4f4
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

  • 167b47c
    Thanks @ardatan! - New options to configure query batching and
    batched delegation

    {
      batchingOptions: {
        dataLoaderOptions: {
          maxBatchSize: 10, // Limits the query batching
        }
      },
      batchDelegateOptions: {
        maxBatchSize: 10, // Limits the batch delegation
      }
    }

    Learn more about these here;
    Batch Delegation
    Query Batching

July 23, 2024

23 Jul 10:36
e742494
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

July 22, 2024

22 Jul 10:48
e5841ae
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

  • d54b21a
    Thanks @ardatan! - If an abstract type on the gateway resolves to a
    type that does not exist on the gateway, return null instead of showing an error to the user

  • d54b21a
    Thanks @ardatan! - If an enum value coming from the subschema is not
    available on gateway, do not show an error to the user but return null instead

@graphql-tools/[email protected]

Patch Changes

July 18, 2024

18 Jul 13:05
108d7b4
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

  • #6356
    8094c37
    Thanks @enisdenjo! - AggregateError errors are GraphQL located
    errors

    Instead of transforming the AggregateError itself to a GraphQL located error.

    This is because of two reasons:

    • AggregateError wont lose the instanceof its class
    • Expanding the AggregateError errors will each contain the proper locations

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

  • #6355
    c6d175b
    Thanks @ardatan! - Handle errors coming from subgraphs correctly
    when a root field is shared by different subgraphs

    • If subgraph A returns an error for Query.foo, and subgraph B returns the data, ignore the
      error and keep it for null fields.
    • If both subgraphs return errors, return them as AggregateError then return them to the gateway
      result.
  • Updated dependencies
    [8094c37,
    97c88a0]:

July 13, 2024

13 Jul 15:57
908bc79
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

July 13, 2024

13 Jul 15:29
791aebf
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

July 05, 2024

05 Jul 16:38
77f5e57
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

July 05, 2024

05 Jul 14:59
d5baf88
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

  • #6299
    b0ffac8
    Thanks @EmrysMyrddin! - When proxying the requests to the HTTP
    executor, it should return `GraphQLError` instances in `errors` array

  • 46eab79
    Thanks @ardatan! - Fixed potential leak on executor disposal

July 05, 2024

05 Jul 11:16
6ae0d90
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Minor Changes

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

Patch Changes

@graphql-tools/[email protected]

Minor Changes

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

Patch Changes

@graphql-tools/[email protected]

Minor Changes

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

Patch Changes

@graphql-tools/[email protected]

Minor Changes

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