Skip to content

Releases: ardatan/graphql-tools

September 26, 2024

26 Sep 18:21
94066a0
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Minor Changes

September 25, 2024

25 Sep 12:34
f9d09c6
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

  • #6536
    3facde0
    Thanks @EmrysMyrddin! - webSocketImpl and lazy options were
    ignored and overriden by default values. This is no longer the case and it's now possible to
    change the WebSocket implementation.

September 11, 2024

11 Sep 20:20
c0592dc
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

August 29, 2024

29 Aug 16:16
f60ac88
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

August 26, 2024

26 Aug 09:56
511b2f1
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

August 26, 2024

26 Aug 08:05
2198808
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

  • #6469
    0e87805
    Thanks @User!! - Handle merged selection sets in the computed fields;

    When a selection set for a computed field needs to be merged, resolve that required selection set
    fully then resolve the computed field. In the following case, the selection set for the author
    field in the Post type is merged with the selection set for the authorId field in the
    Comment type.

    type Query {
      feed: [Post!]!
    }
    
    type Post {
      id: ID! @computed(selectionSet: "{ comments { authorId } }")
    }
    
    type Comment {
      id: ID!
      authorId: ID!
    }
    
    type User {
      id: ID!
      name: String!
    }
    type Post {
      id: ID!
      comments: [Comment!]!
    }
    
    type Comment {
      id: ID!
    }

@graphql-tools/[email protected]

Patch Changes

  • #6469
    0e87805
    Thanks @User!! - Handle merged selection sets in the computed fields;

    When a selection set for a computed field needs to be merged, resolve that required selection set
    fully then resolve the computed field. In the following case, the selection set for the author
    field in the Post type is merged with the selection set for the authorId field in the
    Comment type.

    type Query {
      feed: [Post!]!
    }
    
    type Post {
      id: ID! @computed(selectionSet: "{ comments { authorId } }")
    }
    
    type Comment {
      id: ID!
      authorId: ID!
    }
    
    type User {
      id: ID!
      name: String!
    }
    type Post {
      id: ID!
      comments: [Comment!]!
    }
    
    type Comment {
      id: ID!
    }
  • Updated dependencies
    [0e87805]:

August 21, 2024

21 Aug 06:36
b6d05ee
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

  • f9dd3d6
    Thanks @ardatan! - Details in the extensions when an unexpected
    error occurs;

    {
      "request": {
        "url": "https://api.example.com/graphql",
        "method": "POST",
        "body": {
          "query": "query { hello }"
        }
      },
      "response": {
        "status": 500,
        "statusText": "Internal Server Error",
        "headers": {
          "content-type": "application/json"
        },
        "body": {
          "errors": [
            {
              "message": "Internal Server Error"
            }
          ]
        }
      }
    }

August 16, 2024

16 Aug 02:01
8b4f869
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

August 14, 2024

14 Aug 11:33
600b2ce
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

  • #6441
    52a69ed
    Thanks @ardatan! - Filter errors as null in the projected key

    If the key field has Error, do not send them to the subgraphs as objects but null.

August 14, 2024

14 Aug 09:39
c1756d6
Compare
Choose a tag to compare

@graphql-tools/[email protected]

Patch Changes

  • 2124d7d
    Thanks @ardatan! - Allow invalid path in `getDirectiveExtensions`