April 30, 2024

@graphql-tools/merge@9.0.4

Patch Changes

• #6111 a06dbd2 Thanks @lesleydreyer! - Fix directive merging when directive name is inherited from object prototype (i.e. toString)

@graphql-tools/stitch@9.2.4

Patch Changes

• #6117 67a9c49 Thanks @ardatan! - Add field as an unavailable field only if it is not able to resolve by any other subschema;

  When the following query is sent to the gateway with the following subschemas, the gateway should resolve Category.details from A Subschema using Product resolver instead of trying to resolve by using non-existing Category resolver from A Subschema.

  Previously, the query planner decides to resolve Category.details after resolving Category from C Subschema. But it will be too late to resolve details because Category is not resolvable in A Subschema.

  So the requests for Category.details and the rest of Category should be different.

  So for the following query, we expect a full result;

  query {
    productFromA(id: "1") {
      id
      name
      category {
        id
        name
        details
      }
    }
  }

  # A Subschema
  type Query {
    productFromA(id: ID): Product
    # No category resolver is present
  }
  
  type Product {
    id: ID
    category: Category
  }
  
  type Category {
    details: CategoryDetails
  }

  # B Subschema
  type Query {
    productFromB(id: ID): Product
  }
  type Product {
    id: ID
    name: String
    category: Category
  }
  type Category {
    id: ID
  }

  # C Subschema
  type Query {
    categoryFromC(id: ID): Category
  }
  
  type Category {
    id: ID
    name: String
  }

• Updated dependencies [a06dbd2]:

  • @graphql-tools/merge@9.0.4