- #5913
83c0af0
Thanks @enisdenjo! - dependencies updates:- Updated dependency
@graphql-tools/delegate@^10.0.3
↗︎ (from^10.0.1
, independencies
) - Updated dependency
@graphql-tools/utils@^10.0.13
↗︎ (from^10.0.0
, independencies
)
- Updated dependency
- Updated dependencies [
83c0af0
,83c0af0
]:- @graphql-tools/delegate@10.0.4
- Updated dependencies [
8fba6cc1
,944a68e8
,944a68e8
]:- @graphql-tools/delegate@10.0.0
- @graphql-tools/utils@10.0.0
-
Updated dependencies [
8e80b689
]:- @graphql-tools/delegate@9.0.35
-
#5205
a33097f7
Thanks @ardatan! - dependencies updates:- Added dependency
value-or-promise@^1.0.12
↗︎ (todependencies
)
- Added dependency
-
2f342e43
Thanks @ardatan! - Do not use promises if not async -
Updated dependencies [
2f342e43
]:- @graphql-tools/delegate@9.0.34
-
1c95368a
Thanks @ardatan! - Use ranged versions for dependencies -
Updated dependencies []:
- @graphql-tools/delegate@9.0.31
- Updated dependencies []:
- @graphql-tools/delegate@9.0.30
- Updated dependencies [
f26392a6
]:- @graphql-tools/delegate@9.0.29
- #5104
1913bf91
Thanks @PatrykWalach! - Passkeys
to lazyOptionsFn
- Updated dependencies [
492220cb
]:- @graphql-tools/delegate@9.0.28
- #5055
30bd4d0c
Thanks @renovate! - dependencies updates:- Updated dependency
dataloader@2.2.2
↗︎ (from2.2.1
, independencies
)
- Updated dependency
- Updated dependencies [
30bd4d0c
]:- @graphql-tools/delegate@9.0.27
- #5025
b09ea282
Thanks @renovate! - dependencies updates:- Updated dependency
dataloader@2.2.1
↗︎ (from2.1.0
, independencies
)
- Updated dependency
- Updated dependencies [
b09ea282
,b5c8f640
]:- @graphql-tools/delegate@9.0.26
- @graphql-tools/utils@9.2.1
- Updated dependencies [
a94217e9
,62d074be
]:- @graphql-tools/utils@9.2.0
- @graphql-tools/delegate@9.0.25
- Updated dependencies [
772b948a
]:- @graphql-tools/delegate@9.0.24
- Updated dependencies []:
- @graphql-tools/delegate@9.0.23
- Updated dependencies [
a4d36fcc
,e3ec35ed
]:- @graphql-tools/delegate@9.0.22
- @graphql-tools/utils@9.1.4
- Updated dependencies [
13177794
]:- @graphql-tools/delegate@9.0.21
- Updated dependencies [
904fe770
,904fe770
]:- @graphql-tools/utils@9.1.3
- @graphql-tools/delegate@9.0.19
- Updated dependencies [
13c24883
,b5e6459f
]:- @graphql-tools/delegate@9.0.18
- @graphql-tools/utils@9.1.2
- Updated dependencies [
7411a5e7
]:- @graphql-tools/utils@9.1.1
- @graphql-tools/delegate@9.0.17
- Updated dependencies []:
- @graphql-tools/delegate@9.0.16
- Updated dependencies [
c0639dd0
]:- @graphql-tools/utils@9.1.0
- @graphql-tools/delegate@9.0.15
- Updated dependencies [
d83b1960
]:- @graphql-tools/utils@9.0.1
- @graphql-tools/delegate@9.0.14
- Updated dependencies []:
- @graphql-tools/delegate@9.0.13
- Updated dependencies []:
- @graphql-tools/delegate@9.0.12
- Updated dependencies [
80836fa7
,8f6d3efc
,80836fa7
,80836fa7
,80836fa7
]:- @graphql-tools/utils@9.0.0
- @graphql-tools/delegate@9.0.11
- Updated dependencies [
f7daf777
]:- @graphql-tools/utils@8.13.1
- @graphql-tools/delegate@9.0.10
- Updated dependencies [
df5848b8
,df5848b8
,df5848b8
,df5848b8
]:- @graphql-tools/delegate@9.0.9
- @graphql-tools/utils@8.13.0
- Updated dependencies [
0402894d
]:- @graphql-tools/delegate@9.0.8
- #4738
614a5622
Thanks @ardatan! - Smarter caching for batch delegation by using the selectionSet input
- Updated dependencies [
00c4a1a4
]:- @graphql-tools/delegate@9.0.7
- Updated dependencies [
43c736bd
]:- @graphql-tools/utils@8.12.0
- @graphql-tools/delegate@9.0.6
- Updated dependencies [
71cb4fae
,403ed450
]:- @graphql-tools/utils@8.11.0
- @graphql-tools/delegate@9.0.5
- Updated dependencies [
4fe3d9c0
]:- @graphql-tools/utils@8.10.1
- @graphql-tools/delegate@9.0.4
-
#4640
27bdc237
Thanks @ardatan! - dependencies updates:- Updated dependency
@graphql-tools/delegate@9.0.3
↗︎ (was9.0.2
, independencies
)
- Updated dependency
- Updated dependencies [
0555a972
]:- @graphql-tools/delegate@9.0.3
- Updated dependencies [
29ee7542
]:- @graphql-tools/delegate@9.0.2
- Updated dependencies [
2609d71f
]:- @graphql-tools/utils@8.10.0
- @graphql-tools/delegate@9.0.1
-
#4624
e3167edc
Thanks @n1ru4l! - Fix CommonJS TypeScript resolution withmoduleResolution
node16
ornodenext
-
Updated dependencies [
e3167edc
,d8dc67aa
]:- @graphql-tools/delegate@9.0.0
- @graphql-tools/utils@8.9.1
- Updated dependencies [2a3b45e3]
- @graphql-tools/utils@8.9.0
- @graphql-tools/delegate@8.8.1
- d76a299c: Support TypeScript module resolution.
- Updated dependencies [a0abbbcd]
- Updated dependencies [d76a299c]
- @graphql-tools/utils@8.8.0
- @graphql-tools/delegate@8.8.0
- Updated dependencies [6df204de]
- Updated dependencies [4914970b]
- @graphql-tools/delegate@8.7.12
- @graphql-tools/utils@8.7.0
- 041c5ba1: Use caret range for the tslib dependency
- Updated dependencies [041c5ba1]
- @graphql-tools/delegate@8.7.11
- @graphql-tools/utils@8.6.13
- Updated dependencies [da7ad43b]
- @graphql-tools/utils@8.6.12
- @graphql-tools/delegate@8.7.10
- Updated dependencies [c0762ee3]
- @graphql-tools/utils@8.6.11
- @graphql-tools/delegate@8.7.9
- Updated dependencies [0fc510cb]
- @graphql-tools/utils@8.6.10
- @graphql-tools/delegate@8.7.8
- Updated dependencies [31a33e2b]
- @graphql-tools/utils@8.6.9
- @graphql-tools/delegate@8.7.7
- Updated dependencies [26e4b464]
- @graphql-tools/delegate@8.7.6
- Updated dependencies [cb238877]
- @graphql-tools/utils@8.6.8
- @graphql-tools/delegate@8.7.5
- Updated dependencies [0bbb1769]
- @graphql-tools/delegate@8.7.4
- @graphql-tools/utils@8.6.7
- fe9402af: Bump data-loader and cross-undici-fetch
- Updated dependencies [fe9402af]
- @graphql-tools/delegate@8.7.3
- Updated dependencies [904c0847]
- @graphql-tools/utils@8.6.6
- @graphql-tools/delegate@8.7.2
- @graphql-tools/delegate@8.7.1
- Updated dependencies [d8fd6b94]
- @graphql-tools/delegate@8.7.0
- Updated dependencies [be2c02d7]
- @graphql-tools/utils@8.6.5
- @graphql-tools/delegate@8.6.1
- Updated dependencies [c40e801f]
- Updated dependencies [d36d530b]
- @graphql-tools/delegate@8.6.0
- @graphql-tools/utils@8.6.4
- 0c0c6857: fix - align versions
- Updated dependencies [0c0c6857]
- @graphql-tools/delegate@8.5.4
- 3da3d66c: fix - align versions
- Updated dependencies [3da3d66c]
- @graphql-tools/utils@8.6.3
- 18341363: feat(visitResult): ignore if field not present in visited object
- Updated dependencies [18341363]
- @graphql-tools/delegate@8.5.1
- @graphql-tools/utils@8.6.2
- 51315610: enhance: avoid using globalThis
- Updated dependencies [51315610]
- @graphql-tools/delegate@8.4.3
- @graphql-tools/utils@8.5.4
-
5482c99a: Support graphql-executor
batchDelegateToSchema currently assumes that the source fieldNodes are unique for each request, but this may not be the case when using executors such as graphql-executor. graphql-executor uses memoization to deliver the identical source fieldNodes object across requests, so functions operating on these fieldNodes can be memoized. This change ensures that batches are unique to requests, as long as the context object differs, using the same strategy that stitching makes use of with batch execution (getBatchingExecutor).
- 4bfb3428: enhance: use ^ for tslib dependency
- Updated dependencies [4bfb3428]
- @graphql-tools/delegate@8.4.1
- @graphql-tools/utils@8.5.1
- 149afddb: fix: getting ready for GraphQL v16
- Updated dependencies [149afddb]
- @graphql-tools/delegate@8.3.0
- @graphql-tools/utils@8.4.0
- c5b0719c: feat: GraphQL v16 support
- c5b0719c: enhance(utils): move memoize functions to utils
- Updated dependencies [c5b0719c]
- Updated dependencies [c5b0719c]
- Updated dependencies [c5b0719c]
- Updated dependencies [c5b0719c]
- Updated dependencies [c5b0719c]
- @graphql-tools/delegate@8.2.0
- @graphql-tools/utils@8.2.0
- c8c13ed1: enhance: remove TypeMap and small improvements
- Updated dependencies [c8c13ed1]
- @graphql-tools/delegate@8.1.1
- @graphql-tools/utils@8.1.2
- e50852e6: use version ranges instead of a fixed version for the graphql-tools package versions
- Updated dependencies [631b11bd]
- Updated dependencies [e50852e6]
- @graphql-tools/delegate@8.1.0
- Updated dependencies [2c807ddb]
- @graphql-tools/utils@8.1.1
- @graphql-tools/delegate@8.0.10
- Updated dependencies [9a13357c]
- @graphql-tools/delegate@8.0.9
- Updated dependencies [b9684631]
- Updated dependencies [9ede806a]
- Updated dependencies [67691b78]
- @graphql-tools/utils@8.1.0
- @graphql-tools/delegate@8.0.8
- Updated dependencies [d47dcf42]
- @graphql-tools/delegate@8.0.7
- Updated dependencies [ded29f3d]
- @graphql-tools/delegate@8.0.6
- Updated dependencies [7fdef335]
- @graphql-tools/delegate@8.0.5
- Updated dependencies [04830049]
- @graphql-tools/utils@8.0.2
- @graphql-tools/delegate@8.0.4
- Updated dependencies [b823dbaf]
- @graphql-tools/utils@8.0.1
- @graphql-tools/delegate@8.0.3
- Updated dependencies [d93945fa]
- @graphql-tools/delegate@8.0.2
- c36defbe: fix(delegate): fix ESM import
- Updated dependencies [c36defbe]
- @graphql-tools/delegate@8.0.1
-
dae6dc7b: refactor: ExecutionParams type replaced by Request type
rootValue property is now a part of the Request type.
When delegating with delegateToSchema, rootValue can be set multiple ways:
- when using a custom executor, the custom executor can utilize a rootValue in whichever custom way it specifies.
- when using the default executor (execute/subscribe from graphql-js): -- rootValue can be passed to delegateToSchema via a named option -- rootValue can be included within a subschemaConfig -- otherwise, rootValue is inferred from the originating schema
When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.
- Updated dependencies [af9a78de]
- Updated dependencies [7d3e3006]
- Updated dependencies [9c26b847]
- Updated dependencies [7d3e3006]
- Updated dependencies [d53e3be5]
- Updated dependencies [7d3e3006]
- Updated dependencies [dae6dc7b]
- Updated dependencies [6877b913]
- Updated dependencies [c42e811d]
- Updated dependencies [7d3e3006]
- Updated dependencies [8c8d4fc0]
- Updated dependencies [7d3e3006]
- Updated dependencies [aa43054d]
- Updated dependencies [7d3e3006]
- Updated dependencies [74581cf3]
- Updated dependencies [c0ca3190]
- Updated dependencies [982c8f53]
- Updated dependencies [7d3e3006]
- Updated dependencies [7d3e3006]
- @graphql-tools/utils@8.0.0
- @graphql-tools/delegate@8.0.0
-
161963ac: fix(batch-delegate): only batch together delegations to the same root field
see #2638.
- 29ead57c: fix(batch-delegate): proxy batched errors
- Updated dependencies [1b730f80]
- Updated dependencies [29ead57c]
- @graphql-tools/delegate@7.0.7
-
a9254491: - Resolver validation options should now be set to
error
,warn
orignore
rather thantrue
orfalse
. In previous versions, some of the validators caused errors to be thrown, while some issued warnings. This changes brings consistency to validator behavior.- The
allowResolversNotInSchema
has been renamed torequireResolversToMatchSchema
, to harmonize the naming convention of all the validators. The default setting ofrequireResolversToMatchSchema
iserror
, matching the previous behavior.
-
The
delegateToSchema
return value has matured and been formalized as anExternalObject
, in which all errors are integrated into the GraphQL response, preserving their initial path. Those advanced users accessing the result directly will note the change in error handling. This also allows for the deprecation of unnecessary helper functions includingslicedError
,getErrors
,getErrorsByPathSegment
functions. Only external errors with missing or invalid paths must still be preserved by annotating the remote object with special properties. The newgetUnpathedErrors
function is therefore necessary for retrieving only these errors. Note also the newannotateExternalObject
andmergeExternalObjects
functions, as well as the renaming ofhandleResult
toresolveExternalValue
. -
Transform types and the
applySchemaTransforms
are now relocated to thedelegate
package;applyRequestTransforms
/applyResultTransforms
functions have been deprecated, however, as this functionality has been replaced since v6 by theTransformer
abstraction. -
The
transformRequest
/transformResult
methods are now provided additionaldelegationContext
andtransformationContext
arguments -- these were introduced in v6, but previously optional. -
The
transformSchema
method may wish to create additional delegating resolvers and so it is now provided thesubschemaConfig
and final (non-executable)transformedSchema
parameters. As in v6, thetransformSchema
is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individualtransformSchema
methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers. -
applySchemaTransforms
parameters have been updated to match and support thetransformSchema
parameters above.
-
wrapSchema
andgenerateProxyingResolvers
now only take a single options argument with named properties of typeSubschemaConfig
. The previously possible shorthand version with first argument consisting of aGraphQLSchema
and second argument representing the transforms should be reworked as aSubschemaConfig
object. -
Similarly, the
ICreateProxyingResolverOptions
interface that provides the options for thecreateProxyingResolver
property ofSubschemaConfig
options has been adjusted. Theschema
property previously could be set to aGraphQLSchema
or aSubschemaConfig
object. This property has been removed in favor of asubschemaConfig
property that will always be aSubschemaConfig
object. Thetransforms
property has been removed; transforms should be included within theSubschemaConfig
object.` -
The format of the wrapping schema has solidified. All non-root fields are expected to use identical resolvers, either
defaultMergedResolver
or a custom equivalent, with root fields doing the hard work of proxying. Support for custom merged resolvers throughtcreateMergedResolver
has been deprecated, as custom merging resolvers conflicts when using stitching's type merging, where resolvers are expected to be identical across subschemas. -
The
WrapFields
transform'swrappingResolver
option has been removed, as this complicates multiple wrapping layers, as well as planned functionality to wrap subscription root fields in potentially multiple layers, as the wrapping resolvers may be different in different layers. Modifying resolvers can still be performed by use of an additional transform such asTransformRootFields
orTransformObjectFields
. -
The
ExtendSchema
transform has been removed, as it is conceptually simpler just to usestitchSchemas
with one subschema. -
The
ReplaceFieldsWithFragment
,AddFragmentsByField
,AddSelectionSetsByField
, andAddMergedTypeSelectionSets
transforms has been removed, as they are superseded by theAddSelectionSets
andVisitSelectionSets
transforms. TheAddSelectionSets
purposely takes parsed SDL rather than strings, to nudge end users to parse these strings at build time (when possible), rather than at runtime. Parsing of selection set strings can be performed using theparseSelectionSet
function from@graphql-tools/utils
.
-
stitchSchemas
'smergeTypes
option is now true by default! This causes theonTypeConflict
option to be ignored by default. To useonTypeConflict
to select a specific type instead of simply merging, simply setmergeTypes
to false. -
schemas
argument has been deprecated, usesubschemas
,typeDefs
, ortypes
, depending on what you are stitching. -
When using batch delegation in type merging, the
argsFromKeys
function is now set only via theargsFromKeys
property. Previously, ifargsFromKeys
was absent, it could be read fromargs
. -
Support for fragment hints has been removed in favor of selection set hints.
-
stitchSchemas
now processes allGraphQLSchema
andSubschemaConfig
subschema input into newSubschema
objects, handling schema config directives such aso@computed
as well as generating the final transformed schema, stored as thetransformedSchema
property, if transforms are used. Signatures of theonTypeConflict
,fieldConfigMerger
, andinputFieldConfigMerger
have been updated to include metadata related to the original and transformed subschemas. Note the property name change foronTypeConflict
fromschema
tosubschema
.
- Mocks returning objects with fields set as functions are now operating according to upstream graphql-js convention, i.e. these functions take three arguments,
args
,context
, andinfo
withparent
available asthis
rather than as the first argument.
filterSchema
'sfieldFilter
will now filter all fields across Object, Interface, and Input types. For the previous Object-only behavior, switch to theobjectFieldFilter
option.- Unused
fieldNodes
utility functions have been removed. - Unused
typeContainsSelectionSet
function has been removed, andtypesContainSelectionSet
has been moved to thestitch
package. - Unnecessary
Operation
type has been removed in favor ofOperationTypeNode
from upstream graphql-js. - As above,
applySchemaTransforms
/applyRequestTransforms
/applyResultTransforms
have been removed from theutils
package, as they are implemented elsewhere or no longer necessary.
- The
-
96a7555d: Fix release
Last PATCH release actually transitively updated graphql-tools and @graphql-tools/delegate to use latest MAJOR version of dependencies.
- Updated dependencies [be1a1575]
- @graphql-tools/delegate@7.0.0
- 533d6d53: Bump all packages to allow adjustments
- Updated dependencies [32c3c4f8]
- Updated dependencies [533d6d53]
- @graphql-tools/delegate@6.2.4