Skip to content

July 18, 2024

Compare
Choose a tag to compare
@theguild-bot theguild-bot released this 18 Jul 13:05
· 131 commits to master since this release
108d7b4

@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]: