chore(deps): update dependency @graphql-tools/utils to v10.11.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@graphql-tools/utils (source)	10.5.4 -> 10.11.0

---

Release Notes

ardatan/graphql-tools (@​graphql-tools/utils)

v10.11.0

Compare Source

Minor Changes

• #​7588
  2118a80
  Thanks @​EmrysMyrddin! - Add optional schema coordinate in error
  extensions. This extension allows to precisely identify the source of the error by automated tools
  like tracing or monitoring.

  This new feature is opt-in, you have to enable it using schemaCoordinateInErrors executor
  option.

  Caution: This feature, when enabled, will expose information about your schema. If you need to
  keep your schema private and secret, you should strip this attribute at serialization time before
  sending errors to the client.

  import { parse } from 'graphql'
  import { normalizedExecutor } from '@​graphql-tools/executor'
  import { getSchemaCoordinate } from '@​graphql-tools/utils'
  import schema from './schema'
  
  const result = await normalizedExecutor({
    schema,
    document: parse(`...`),
    schemaCoordinateInErrors: true // enable adding schema coordinate to graphql errors
  })
  
  if (result.errors) {
    for (const error of result.errors) {
      console.log('Error in resolver ', error.coordinate, ':', error.message)
      // or with `getSchemaCoordinate` util, to workaround types if needed
      console.log('Error in resolver', getSchemaCoordinate(error), ':', error.message)
    }
  }

v10.10.3

Compare Source

Patch Changes

• #​7683
  2fe123a
  Thanks @​ardatan! - Revert
  #​7683 which can cause unexpected breaking changes so
  as before the schema extension node will always be converted to a schema definition node

v10.10.2

Compare Source

Patch Changes

• #​7679
  dddc5f6
  Thanks @​ardatan! - Support "federation/subgraph style" schemas in
  astFromSchema and printSchemaWithDirectives

  If a GraphQLSchema doesn't have any defined operation types, we should print the schema
  definition as an extension rather than omitting it entirely. They are not a valid schema on their
  own, but they are valid subgraph schemas in a federation setup, and it is possible to build such
  schemas with assumeValid options.

  // A schema without defined root types
  buildSchema(
    /* GraphQL */ `
      extend schema @​link(url: "https://specs.apollo.dev/federation/v2.0", import: ["@​key"])
  
      type User @​key(fields: "id") {
        id: ID!
        username: String
      }
    `,
    { assumeValid: true, assumeValidSDL: true }
  )

v10.10.1

Compare Source

Patch Changes

• fbb58b5
  Thanks @​ardatan! - Remove `dset` dependency

v10.10.0

Compare Source

Minor Changes

• #​5269
  fded91e
  Thanks @​uroslates! - Add default values to the arguments

  When the schema is like following;

  type Query {
      getAllPages(currentPage: Int = 0, pageSize: Int = 10, pageType: getAllPages_pageType = ContentPage, sort: String = "asc"): PagesList
  }
  
  enum getAllPages_pageType {
      ContentPage
      CategoryPage
      CatalogPage
  }
  
  type PagesList {
      ...
  }

  The generated operation will be like following;

  query getAllPages_query($currentPage: Int = 0, $pageSize: Int = 10, $pageType: getAllPages_pageType = ContentPage, $sort: String = "asc") {
      getAllPages(currentPage: $currentPage, pageSize: $pageSize, pageType: $pageType, sort: $sort) {
          ...
      }
  }

Patch Changes

• #​7012
  fd105f4
  Thanks @​ardatan! - Fix the bug in mergeDeep;

  The following inputs and outputs are corrected;

  • mergeDeep([{a:2}, undefined]) - Any nullish values should be ignored so it should return
    {a:2}
  • mergeDeep([]) - no sources should return undefined
  • mergeDeep([undefined]) - no sources should return undefined

• #​5294
  3b99a9b
  Thanks @​n1ru4l! - Do not map builtin scalars

v10.9.1

Compare Source

Patch Changes

• 32d0457
  Thanks @​ardatan! - Fix oneOf handling

v10.9.0

Compare Source

Minor Changes

• #​7281
  53db005
  Thanks @​EmrysMyrddin! - Add optional subgraphName preoperty
  to the ExecutionRequest interface for usage in Gateways like Hive Gateway.

Patch Changes

• #​7282
  22af985
  Thanks @​renovate! - Support @oneOf directive

v10.8.6

Compare Source

Patch Changes

• d123e26
  Thanks @​ardatan! - Fix incomplete string escaping/encoding

v10.8.5

Compare Source

Patch Changes

• #​6977
  90a717e
  Thanks @​ardatan! - In executor, do not use leaking
  registerAbortSignalListener, and handle listeners inside the execution context

• #​7025
  26518de
  Thanks @​ardatan! - Better handling for field name handling in
  buildOperationForField

v10.8.4

Compare Source

Patch Changes

• 155944b
  Thanks @​ardatan! - Fix breaking change by adding
  PromiseWithResolvers back

v10.8.3

Compare Source

Patch Changes

• #​6971
  4a2eb14
  Thanks @​ardatan! - dependencies updates:
  • Added dependency
    @whatwg-node/promise-helpers@^1.0.0 ↗︎
    (to dependencies)

v10.8.2

Compare Source

Patch Changes

• 3547bba
  Thanks @​ardatan! - Relax extensions type

v10.8.1

Compare Source

Patch Changes

• 651a5dc
  Thanks @​ardatan! - Fix the regression on var counting

v10.8.0

Compare Source

Minor Changes

• #​6921
  357b2ee
  Thanks @​renovate! - New isUrl helper, and it uses
  URL.canParse if available

Patch Changes

• 0a3e193
  Thanks @​ardatan! - Do not add _v prefix if there is only one
  argument/variable

v10.7.2

Compare Source

Patch Changes

• #​6822
  53bb601
  Thanks @​enisdenjo! - dependencies updates:

  • Updated dependency dset@^3.1.4 ↗︎ (from
    ^3.1.2, in dependencies)

• #​6822
  53bb601
  Thanks @​enisdenjo! - Bump dset dependency handling the
  CVE-2024-21529

  https://security.snyk.io/vuln/SNYK-JS-DSET-7116691

v10.7.1

Compare Source

Patch Changes

• #​6809
  4912f19
  Thanks @​AaronMoat! - Remove use of VoidFunction type, which
  requires DOM types

v10.7.0

Compare Source

Minor Changes

• #​6789
  2c70d27
  Thanks @​n1ru4l! - - New helper function getAbortPromise to get a
  promise rejected when AbortSignal is aborted

  • New helper function registerAbortSignalListener to register a listener to abort a promise when
    AbortSignal is aborted

  Instead of using .addEventListener('abort', () => {/* ... */}), we register a single listener to
  avoid warnings on Node.js like
  MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 abort listeners added. Use emitter.setMaxListeners() to increase limit.

v10.6.4

Compare Source

Patch Changes

• #​6769
  6a8123b
  Thanks @​ardatan! - Improvements for fakePromise so it can be used
  without params to create a void Promise

v10.6.3

Compare Source

Patch Changes

• 020b9e4
  Thanks @​ardatan! - `AbortSignal` in `GraphQLResolveInfo`, and
  `AbortSignal` in `ExecutionRequest`

v10.6.2

Compare Source

Patch Changes

• #​6737
  1b24656
  Thanks @​ardatan! - Handle array of primitives correctly

  The bug was following;

  mergeDeep([{ options: ['$a', '$b'] }, { options: ['$c'] }, { options: ['$d', '$e'] }])
  
  // results in { options: [{}, {}] }

v10.6.1

Compare Source

Patch Changes

• 1e02935
  Thanks @​ardatan! - Handle parse errors correctly when loader gets a
  string directly

v10.6.0

Compare Source

Minor Changes

• 414e404
  Thanks @​ardatan! - new fakePromise, mapMaybePromise and
  fakeRejectPromise helper functions

v10.5.6

Compare Source

Patch Changes

• #​6677
  dc5043b
  Thanks @​enisdenjo! - onError and onEnd callbacks from
  mapAsyncIterator are invoked only once regardless of how many times throw/return was called
  on the iterator

v10.5.5

Compare Source

Patch Changes

• #​6524
  cf2ce5e
  Thanks @​kachkaev! - Make two types compatible with strict tsc
  config

---

Configuration

📅 Schedule: Branch creation - "after 10pm,before 1am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.