May 02, 2024

@graphql-tools/[email protected]

Patch Changes

• 361052a Thanks @ardatan! - Small fix: check all final types to find orphan interfaces

May 02, 2024

@graphql-tools/[email protected]

Patch Changes

• #6126 680351e Thanks @ardatan! - When there is a Node subschema, and others to resolve the rest of the entities by using a union resolver as in Federation like below, it was failing. This version fixes that issue.

  query {
    node(id: "1") {
      id # Fetches from Node
      ... on User {
        name # Fetches from User
      }
    }
  }

  type Query {
    node(id: ID!): Node
  }
  
  interface Node {
    id: ID!
  }
  
  type User implements Node {
    id: ID!
  }
  
  type Post implements Node {
    id: ID!
  }

  # User subschema
  scalar _Any
  type Query {
    _entities(representations: [_Any!]!): [_Entity]!
  }
  union _Entity = User
  interface Node {
    id: ID!
  }
  type User implements Node {
    id: ID!
    name: String!
  }

  # Post subschema
  scalar _Any
  union _Entity = Post
  type Query {
    _entities(representations: [_Any!]!): [_Entity]!
  }
  interface Node {
    id: ID!
  }
  type Post implements Node {
    id: ID!
    title: String!
  }

@graphql-tools/[email protected]

Patch Changes

• #6126 680351e Thanks @ardatan! - When there is a Node subschema, and others to resolve the rest of the entities by using a union resolver as in Federation like below, it was failing. This version fixes that issue.

  query {
    node(id: "1") {
      id # Fetches from Node
      ... on User {
        name # Fetches from User
      }
    }
  }

  type Query {
    node(id: ID!): Node
  }
  
  interface Node {
    id: ID!
  }
  
  type User implements Node {
    id: ID!
  }
  
  type Post implements Node {
    id: ID!
  }

  # User subschema
  scalar _Any
  type Query {
    _entities(representations: [_Any!]!): [_Entity]!
  }
  union _Entity = User
  interface Node {
    id: ID!
  }
  type User implements Node {
    id: ID!
    name: String!
  }

  # Post subschema
  scalar _Any
  union _Entity = Post
  type Query {
    _entities(representations: [_Any!]!): [_Entity]!
  }
  interface Node {
    id: ID!
  }
  type Post implements Node {
    id: ID!
    title: String!
  }

• Updated dependencies [680351e]:

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

@graphql-tools/[email protected]

Patch Changes

• #6126 680351e Thanks @ardatan! - When there is a Node subschema, and others to resolve the rest of the entities by using a union resolver as in Federation like below, it was failing. This version fixes that issue.

  query {
    node(id: "1") {
      id # Fetches from Node
      ... on User {
        name # Fetches from User
      }
    }
  }

  type Query {
    node(id: ID!): Node
  }
  
  interface Node {
    id: ID!
  }
  
  type User implements Node {
    id: ID!
  }
  
  type Post implements Node {
    id: ID!
  }

  # User subschema
  scalar _Any
  type Query {
    _entities(representations: [_Any!]!): [_Entity]!
  }
  union _Entity = User
  interface Node {
    id: ID!
  }
  type User implements Node {
    id: ID!
    name: String!
  }

  # Post subschema
  scalar _Any
  union _Entity = Post
  type Query {
    _entities(representations: [_Any!]!): [_Entity]!
  }
  interface Node {
    id: ID!
  }
  type Post implements Node {
    id: ID!
    title: String!
  }

• Updated dependencies [680351e]:

  • @graphql-tools/[email protected]

May 02, 2024

@graphql-tools/[email protected]

Patch Changes

• 98b2795 Thanks @ardatan! - Improvements on unavailable field selection, and key object projection

• Updated dependencies [98b2795]:

  • @graphql-tools/[email protected]

@graphql-tools/[email protected]

Patch Changes

• 98b2795 Thanks @ardatan! - Improvements on unavailable field selection, and key object projection

May 02, 2024

@graphql-tools/[email protected]

Patch Changes

• 4ce3ffc Thanks @ardatan! - Simplify the logic in wrapConcreteTypes

@graphql-tools/[email protected]

Patch Changes

• 9238e14 Thanks @ardatan! - Improvements on field merging and extraction of unavailable fields

• Updated dependencies [9238e14, 4ce3ffc]:

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

@graphql-tools/[email protected]

Patch Changes

• 9238e14 Thanks @ardatan! - Improvements on field merging and extraction of unavailable fields

• Updated dependencies [4ce3ffc]:

  • @graphql-tools/[email protected]

April 30, 2024

@graphql-tools/[email protected]

Patch Changes

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

@graphql-tools/[email protected]

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/[email protected]

April 29, 2024

@graphql-tools/[email protected]

Patch Changes

• #6109 074fad4 Thanks @ardatan! - Merge list fields correctly

@graphql-tools/[email protected]

Patch Changes

• #6109 074fad4 Thanks @ardatan! - Show responses in debug logging with DEBUG env var

• Updated dependencies [074fad4, 074fad4]:

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

@graphql-tools/[email protected]

Patch Changes

• #6109 074fad4 Thanks @ardatan! - Exclude fields with __typename while extracting missing fields for the type merging

• Updated dependencies [074fad4]:

  • @graphql-tools/[email protected]

April 29, 2024

@graphql-tools/[email protected]

Patch Changes

• #6107 b281dd6 Thanks @ardatan! - Fix the priority of isolated fields

April 29, 2024

@graphql-tools/[email protected]

Patch Changes

• #6105 5567347 Thanks @ardatan! - Handle fields in unmerged types as both isolated and non-isolated fields

• #6105 5567347 Thanks @ardatan! - Respect specifiedByURL in stitched schemas

• Updated dependencies [5567347, 5567347]:

  • @graphql-tools/[email protected]

@graphql-tools/[email protected]

Minor Changes

• #6105 5567347 Thanks @ardatan! - Add enumValueFilter and directiveFilter to filterSchema

Patch Changes

• #6105 5567347 Thanks @ardatan! - Handle fields in unmerged types as both isolated and non-isolated fields

April 26, 2024

@graphql-tools/[email protected]

Patch Changes

• #6100 4e72868 Thanks @JohanBrorson! - Remove unused dependencies json-stable-stringify and @types/json-stable-stringify.

April 26, 2024

@graphql-tools/[email protected]

Patch Changes

• af7be09 Thanks @ardatan! - Hotfix: do not use nullable and nonNullable prefixes if field names don't match