@graphql-tools/executor@1.5.0
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
schemaCoordinateInErrorsexecutor
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) } }
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/executor-apollo-link@2.0.5
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/executor-envelop@4.0.5
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/executor-legacy-ws@1.1.24
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/executor-urql-exchange@1.0.27
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/executor-yoga@3.0.35
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
- @graphql-tools/executor-envelop@4.0.5
@graphql-tools/graphql-tag-pluck@8.3.26
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
graphql-tools@9.0.25
Patch Changes
- Updated dependencies []:
- @graphql-tools/schema@10.0.30
@graphql-tools/import@7.1.8
Patch Changes
-
#7588
2118a80
Thanks @EmrysMyrddin! - dependencies updates:- Updated dependency
@theguild/federation-composition@^0.21.0↗︎
(from^0.20.2, independencies)
- Updated dependency
-
#7721
92f1622
Thanks @renovate! - dependencies updates:- Updated dependency
@theguild/federation-composition@^0.21.0↗︎
(from^0.20.2, independencies)
- Updated dependency
-
Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/links@10.0.5
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/load@8.1.7
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
- @graphql-tools/schema@10.0.30
@graphql-tools/apollo-engine-loader@8.0.27
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/code-file-loader@8.1.27
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
- @graphql-tools/graphql-tag-pluck@8.3.26
@graphql-tools/git-loader@8.0.31
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
- @graphql-tools/graphql-tag-pluck@8.3.26
@graphql-tools/github-loader@9.0.5
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
- @graphql-tools/graphql-tag-pluck@8.3.26
@graphql-tools/graphql-file-loader@8.1.8
Patch Changes
- #7588
2118a80
Thanks @EmrysMyrddin! - dependencies updates:- Updated dependency
@graphql-tools/import@7.1.7↗︎
(from7.1.6, independencies)
- Updated dependency
- Updated dependencies
[2118a80,
92f1622,
2118a80]:- @graphql-tools/import@7.1.8
- @graphql-tools/utils@10.11.0
@graphql-tools/json-file-loader@8.0.25
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/module-loader@8.0.25
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/url-loader@9.0.5
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
- @graphql-tools/executor-legacy-ws@1.1.24
@graphql-tools/merge@9.1.6
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/mock@9.1.4
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
- @graphql-tools/schema@10.0.30
@graphql-tools/node-require@7.0.33
Patch Changes
- #7588
2118a80
Thanks @EmrysMyrddin! - dependencies updates:- Updated dependency
@graphql-tools/graphql-file-loader@8.1.7↗︎
(from8.1.6, independencies)
- Updated dependency
- Updated dependencies
[2118a80,
2118a80]:- @graphql-tools/graphql-file-loader@8.1.8
- @graphql-tools/utils@10.11.0
- @graphql-tools/load@8.1.7
@graphql-tools/relay-operation-optimizer@7.0.26
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/resolvers-composition@7.0.25
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
@graphql-tools/schema@10.0.30
Patch Changes
- Updated dependencies
[2118a80]:- @graphql-tools/utils@10.11.0
- @graphql-tools/merge@9.1.6
@graphql-tools/utils@10.11.0
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
schemaCoordinateInErrorsexecutor
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) } }