Releases: ardatan/graphql-tools
August 12, 2024
August 12, 2024
August 11, 2024
@graphql-tools/federation@2.2.6
Patch Changes
-
b8bf584
Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
directive handling in the extensions -
Updated dependencies
[b8bf584
]:- @graphql-tools/utils@10.4.0
- @graphql-tools/schema@10.0.5
- @graphql-tools/merge@9.0.5
@graphql-tools/merge@9.0.5
Patch Changes
-
b8bf584
Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
directive handling in the extensions -
Updated dependencies
[b8bf584
]:- @graphql-tools/utils@10.4.0
@graphql-tools/schema@10.0.5
Patch Changes
-
b8bf584
Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
directive handling in the extensions -
Updated dependencies
[b8bf584
]:- @graphql-tools/utils@10.4.0
- @graphql-tools/merge@9.0.5
@graphql-tools/utils@10.4.0
Minor Changes
August 08, 2024
@graphql-tools/federation@2.2.5
Patch Changes
-
dbb0516
Thanks @ardatan! - If there are repeated computed fields like below,
project the data for the computed fields for eachfields
and merge them correctly. And if they
are array as inuserOrders
, merge them by respecting the order (the second one can haveprice
maybe).type UserOrder @key(fields: "id") { id: ID! status: String! price: Int! } type User @key(fields: "id") { id: ID! userOrders: [UserOrder!] @external totalOrdersPrices: Int @requires(fields: "userOrders { id }") aggregatedOrdersByStatus: Int @requires(fields: "userOrders { id }") }
August 07, 2024
@graphql-tools/delegate@10.0.18
Patch Changes
-
#6420
a867bbc
Thanks @ardatan! - dependencies updates:- Added dependency
@repeaterjs/repeater@^3.0.6
↗︎
(todependencies
)
- Added dependency
-
#6420
a867bbc
Thanks @ardatan! - Pass operation directives correctly to the
subschema;query { hello @someDir }
-
#6418
da93c08
Thanks @ardatan! - Fix extra inline fragments for all abstract types
in the upstream schema callIf there are two subschemas like below, the final
Node
interface is implemented by bothOven
andToaster
while they are not implemented in both schemas. In this case the query
{ products { id ... on Node { id } } }
will need to be transformed to
{ products { id ... on Oven { id } ... on Node { id } } }
for the first subschema. But
previously the query planner was automatically creating inline fragments for all possible types
which was not optimal. Now it adds inline fragments only if this case is seen.type Query { products: [Product] } union Product = Oven | Toaster interface Node { id: ID! } type Oven { id: ID! } type Toaster implements Node { id: ID! warranty: Int }
And another one like below;
interface Node { id: ID! } type Oven implements Node { id: ID! warranty: Int }
-
Updated dependencies
[a867bbc
]:- @graphql-tools/executor@1.3.1
- @graphql-tools/utils@10.3.4
@graphql-tools/executor@1.3.1
Patch Changes
-
#6420
a867bbc
Thanks @ardatan! -mapAsyncIterator
now acceptsAsyncIterable
-
Updated dependencies
[a867bbc
]:- @graphql-tools/utils@10.3.4
@graphql-tools/utils@10.3.4
Patch Changes
August 05, 2024
cross-inspect@1.0.1
Patch Changes
- #6385
d0f7d75
Thanks @tobiasdiez! - remove generic package export
@graphql-tools/utils@10.3.3
Patch Changes
-
#6385
d0f7d75
Thanks @tobiasdiez! - remove generic package export -
Updated dependencies
[d0f7d75
]:- cross-inspect@1.0.1
August 03, 2024
@graphql-tools/graphql-tag-pluck@8.3.2
Patch Changes
- #6407
d4d3691
Thanks @dimaMachina! - fixrequire is not defined
for esm
build
@graphql-tools/code-file-loader@8.1.3
Patch Changes
- Updated dependencies
[d4d3691
]:- @graphql-tools/graphql-tag-pluck@8.3.2
@graphql-tools/git-loader@8.0.7
Patch Changes
- Updated dependencies
[d4d3691
]:- @graphql-tools/graphql-tag-pluck@8.3.2