August 12, 2024

@graphql-tools/[email protected]

Minor Changes

• 8fd7703
  Thanks @ardatan! - Export getDirectiveExtensions

August 11, 2024

@graphql-tools/[email protected]

Patch Changes

• b8bf584
  Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
  directive handling in the extensions

• Updated dependencies
  [b8bf584]:

  • @graphql-tools/[email protected]
  • @graphql-tools/[email protected]
  • @graphql-tools/[email protected]

@graphql-tools/[email protected]

Patch Changes

• b8bf584
  Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
  directive handling in the extensions

• Updated dependencies
  [b8bf584]:

  • @graphql-tools/[email protected]

@graphql-tools/[email protected]

Patch Changes

• b8bf584
  Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
  directive handling in the extensions

• Updated dependencies
  [b8bf584]:

  • @graphql-tools/[email protected]
  • @graphql-tools/[email protected]

@graphql-tools/[email protected]

Minor Changes

• b8bf584
  Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
  directive handling in the extensions

August 08, 2024

@graphql-tools/[email protected]

Patch Changes

• dbb0516
  Thanks @ardatan! - If there are repeated computed fields like below,
  project the data for the computed fields for each fields and merge them correctly. And if they
  are array as in userOrders, merge them by respecting the order (the second one can have price
  maybe).

  type UserOrder @key(fields: "id") {
    id: ID!
    status: String!
    price: Int!
  }
  
  type User @key(fields: "id") {
    id: ID!
    userOrders: [UserOrder!] @external
    totalOrdersPrices: Int @requires(fields: "userOrders { id }")
    aggregatedOrdersByStatus: Int @requires(fields: "userOrders { id }")
  }

August 07, 2024

@graphql-tools/[email protected]

Patch Changes

• #6420
  a867bbc
  Thanks @ardatan! - dependencies updates:

  • Added dependency
    @repeaterjs/repeater@^3.0.6 ↗︎
    (to dependencies)

• #6420
  a867bbc
  Thanks @ardatan! - Pass operation directives correctly to the
  subschema;

  query {
    hello @someDir
  }

• #6418
  da93c08
  Thanks @ardatan! - Fix extra inline fragments for all abstract types
  in the upstream schema call

  If there are two subschemas like below, the final Node interface is implemented by both Oven
  and Toaster while they are not implemented in both schemas. In this case the query
  { products { id ... on Node { id } } } will need to be transformed to
  { products { id ... on Oven { id } ... on Node { id } } } for the first subschema. But
  previously the query planner was automatically creating inline fragments for all possible types
  which was not optimal. Now it adds inline fragments only if this case is seen.

  type Query {
    products: [Product]
  }
  
  union Product = Oven | Toaster
  
  interface Node {
    id: ID!
  }
  
  type Oven {
    id: ID!
  }
  
  type Toaster implements Node {
    id: ID!
    warranty: Int
  }

  And another one like below;

  interface Node {
    id: ID!
  }
  
  type Oven implements Node {
    id: ID!
    warranty: Int
  }

• Updated dependencies
  [a867bbc]:

  • @graphql-tools/[email protected]
  • @graphql-tools/[email protected]

@graphql-tools/[email protected]

Patch Changes

• #6420
  a867bbc
  Thanks @ardatan! - mapAsyncIterator now accepts AsyncIterable

• Updated dependencies
  [a867bbc]:

  • @graphql-tools/[email protected]

@graphql-tools/[email protected]

Patch Changes

• #6420
  a867bbc
  Thanks @ardatan! - mapAsyncIterator now accepts AsyncIterable

August 05, 2024

[email protected]

Patch Changes

• #6385
  d0f7d75
  Thanks @tobiasdiez! - remove generic package export

@graphql-tools/[email protected]

Patch Changes

• #6385
  d0f7d75
  Thanks @tobiasdiez! - remove generic package export

• Updated dependencies
  [d0f7d75]:

  • [email protected]

August 03, 2024

@graphql-tools/[email protected]

Patch Changes

• #6407
  d4d3691
  Thanks @dimaMachina! - fix require is not defined for esm
  build

@graphql-tools/[email protected]

Patch Changes

• Updated dependencies
  [d4d3691]:
  • @graphql-tools/[email protected]

@graphql-tools/[email protected]

Patch Changes

• Updated dependencies
  [d4d3691]:
  • @graphql-tools/[email protected]

August 01, 2024

@graphql-tools/[email protected]

Patch Changes

• #6403
  3803897
  Thanks @ardatan! - Cleanup extra fields, empty inline fragments and
  duplicate __typename fields

@graphql-tools/[email protected]

Patch Changes

• #6403
  3803897
  Thanks @ardatan! - Cleanup extra fields, empty inline fragments and
  duplicate __typename fields

• Updated dependencies
  [3803897]:

  • @graphql-tools/[email protected]

July 31, 2024

@graphql-tools/[email protected]

Patch Changes

• 0d203ab
  Thanks @ardatan! - Support @requires with arguments like
  @requires(fields: "price(currency: 'USD')")

July 30, 2024

@graphql-tools/[email protected]

Patch Changes

• 79faf07
  Thanks @ardatan! - Do not use `entryPoints` if there is only one

July 30, 2024

@graphql-tools/[email protected]

Patch Changes

• 63cab60
  Thanks @ardatan! - Use type definition merger instead of
  `concatAST` to merge type definitions for creating a subschema for Federation