Releases: ardatan/graphql-tools
July 13, 2024
@graphql-tools/executor-http@1.1.3
Patch Changes
-
#6332
7be6930
Thanks @kamilkisiela! - Strip ignored characters when printing
a query in executor-http -
Updated dependencies
[a276ba8
]:- @graphql-tools/utils@10.3.2
@graphql-tools/utils@10.3.2
Patch Changes
July 05, 2024
July 05, 2024
@graphql-tools/executor-http@1.1.1
Patch Changes
-
#6299
b0ffac8
Thanks @EmrysMyrddin! - When proxying the requests to the HTTP
executor, it should return `GraphQLError` instances in `errors` array -
46eab79
Thanks @ardatan! - Fixed potential leak on executor disposal
July 05, 2024
@graphql-tools/executor-graphql-ws@1.2.0
Minor Changes
- #6323
cacf20f
Thanks @ardatan! - Implement Symbol.dispose or Symbol.asyncDispose
to make `Executor`s `Disposable`
Patch Changes
- Updated dependencies
[cacf20f
]:- @graphql-tools/utils@10.3.0
@graphql-tools/executor-http@1.1.0
Minor Changes
- #6323
cacf20f
Thanks @ardatan! - Implement Symbol.dispose or Symbol.asyncDispose
to make `Executor`s `Disposable`
Patch Changes
- Updated dependencies
[cacf20f
]:- @graphql-tools/utils@10.3.0
@graphql-tools/executor-legacy-ws@1.1.0
Minor Changes
- #6323
cacf20f
Thanks @ardatan! - Implement Symbol.dispose or Symbol.asyncDispose
to make `Executor`s `Disposable`
Patch Changes
- Updated dependencies
[cacf20f
]:- @graphql-tools/utils@10.3.0
@graphql-tools/utils@10.3.0
Minor Changes
July 03, 2024
July 01, 2024
@graphql-tools/delegate@10.0.12
Patch Changes
@graphql-tools/executor@1.2.8
Patch Changes
-
#6306
74f995f
Thanks @n1ru4l! - Properly propagate the original error in custom
scalars.Errors thrown in the
parseValue
function for custom scalars were not propagated correctly using
theoriginalError
property of theGraphQLError
on invalid input. As a result, error codes from
theextensions.code
were not propagated correctly. -
Updated dependencies
[66c99d9
]:- @graphql-tools/utils@10.2.3
@graphql-tools/federation@2.1.1
Patch Changes
-
#6293
3f301dc
Thanks @ardatan! - Do not useentryPoints
forMergedTypeConfig
if there is only one -
#6278
66c99d9
Thanks @ardatan! - Exclude@defer
in the subgraph requests -
Updated dependencies
[66c99d9
,
3f301dc
]:- @graphql-tools/delegate@10.0.12
- @graphql-tools/stitch@9.2.10
- @graphql-tools/utils@10.2.3
@graphql-tools/stitch@9.2.10
Patch Changes
-
#6293
3f301dc
Thanks @ardatan! - Do not apply isolation for Mutation fields -
Updated dependencies
[66c99d9
,
74f995f
]:- @graphql-tools/delegate@10.0.12
- @graphql-tools/utils@10.2.3
- @graphql-tools/executor@1.2.8
@graphql-tools/utils@10.2.3
Patch Changes
June 21, 2024
@graphql-tools/executor@1.2.7
Patch Changes
-
#6280
7dcd0af
Thanks @ardatan! - Since the executor is version agnostic, it should
respect the schemas created with older versions.So if a type resolver returns a type instead of type name which is required since
graphql@16
,
the executor should handle it correctly.See the following example:
// Assume that the following code is executed with `graphql@15` import { execute } from '@graphql-tools/executor' const BarType = new GraphQLObjectType({ name: 'Bar', fields: { bar: { type: GraphQLString, resolve: () => 'bar' } } }) const BazType = new GraphQLObjectType({ name: 'Baz', fields: { baz: { type: GraphQLString, resolve: () => 'baz' } } }) const BarBazType = new GraphQLUnionType({ name: 'BarBaz', types: [BarType, BazType], // This is the resolver that returns the type instead of type name resolveType(obj) { if ('bar' in obj) { return BarType } if ('baz' in obj) { return BazType } } }) const QueryType = new GraphQLObjectType({ name: 'Query', fields: { barBaz: { type: BarBazType, resolve: () => ({ bar: 'bar' }) } } }) const schema = new GraphQLSchema({ query: QueryType }) const result = await execute({ schema, document: parse(/* GraphQL */ ` query { barBaz { ... on Bar { bar } ... on Baz { baz } } } `) }) expect(result).toEqual({ data: { barBaz: { bar: 'bar' } } })
June 18, 2024
@graphql-tools/federation@2.1.0
Minor Changes
-
#6267
d5dd794
Thanks @EmrysMyrddin! - AdddelayInSeconds
to thefailure
event to give users more control on failure handling. -
#6267
d5dd794
Thanks @EmrysMyrddin! - Add a the ability to start polling with
a delay. This ease the handling of failure handling, allowing to restart the manager and
respecting GraphOS minimum retry delay.
Patch Changes
- #6267
d5dd794
Thanks @EmrysMyrddin! - Fix Supergraph Manager Event Emitter
not calling every listener when at least one has been registered usingonce
method.
June 11, 2024
@graphql-tools/federation@2.0.1
Patch Changes
-
#6238
0f7059b
Thanks @ardatan! - Merge the elements of the lists if the root field
is shared across different subgraphstype Query { products: [Product] # If this field is returned by multiple subgraphs, the elements of the lists will be merged }
-
Updated dependencies
[0f7059b
]:- @graphql-tools/utils@10.2.2
@graphql-tools/utils@10.2.2
Patch Changes
June 04, 2024
@graphql-tools/executor-envelop@3.0.0
Major Changes
- #6227
85c383f
Thanks @ardatan! - BREAKING:invalidateSupergraph
is now replaced
withinvalidateUnifiedGraph
@graphql-tools/executor-yoga@3.0.0
Major Changes
- #6227
85c383f
Thanks @ardatan! - BREAKING:invalidateSupergraph
is now replaced
withinvalidateUnifiedGraph
Patch Changes
- Updated dependencies
[85c383f
]:- @graphql-tools/executor-envelop@3.0.0
@graphql-tools/federation@2.0.0
Major Changes
- #6227
85c383f
Thanks @ardatan! - BREAKING CHANGES:getSubschemasFromSupergraphSdl
has been removed in favor of the new
getStitchingOptionsFromSupergraphSdl
, and it returns the options forstitchSchemas
instead
of the map of subschemasonExecutor
has been removed in favor ofonSubschemaConfig
- To change the default HTTP executor options, use
httpExecutorOpts
instead ofonExecutor
Patch Changes
- #6223
db29280
Thanks @EmrysMyrddin! - dependencies updates:- Added dependency
@whatwg-node/fetch@^0.9.17
↗︎
(todependencies
)
- Added dependency