Useful tools to create and manipulate GraphQL schemas.
A fully open-source MIT-licensed GraphQL API gateway that can act as a GraphQL federation Gateway or a Proxy Gateway for any GraphQL services.
It can be run as a standalone binary, a Docker Image, or as a JavaScript package (e.g. within Node.js, Bun, Deno, Google Cloud Functions, Azure Functions or Cloudflare Workers)
graphql-hiveed323fa]:#1144 54beb7a Thanks @ardatan! - dependencies updates:
@whatwg-node/fetch@^0.10.8 ↗︎ (from ^0.10.6, in dependencies)#1187 85d7c95 Thanks @enisdenjo! - Handle nested keys with arguments
#1136 511ba36 Thanks @ardatan! - Handle errors on non-nullable fields in shared root fields correctly
Updated dependencies [54beb7a, 4a80de1]:
0512be3 Thanks @ardatan! - Optimizes @provides handling by avoiding the generation of new query plans when a parent subgraph already supplies the requested fields.subtractSelectionSets to compute leftover selections.providedSelectionNode through planning to subtract out provided fields early.b7627d3, ef0e24c, 0512be3, b7627d3]:#1045 da47a0e Thanks @enisdenjo! - dependencies updates:
@whatwg-node/fetch@^0.10.6 ↗︎ (from ^0.10.4, in dependencies)#1045 da47a0e Thanks @enisdenjo! - Update graphql-yoga and whatwg-node packages
In light of https://github.com/ardatan/whatwg-node/pull/2305. Please upgrade as soon as possible!
#997 4cf75cb Thanks @ardatan! - - BREAKING: HTTP Executor no longer takes serviceName as an option.
@graphql-mesh/transport-http-callback no longer handle DOWNSTREAM_SERVICE_ERROR error code with serviceName.DOWNSTREAM_SERVICE_ERROR error code and serviceName as a property. This behavior can be configured with subgraphErrors option of the createGatewayRuntime function or CLI config.subgraphError: {
errorCode: 'DOWNSTREAM_SERVICE_ERROR', // or `false` to remove this code completely
subgraphNameProp: 'serviceName' // or `false` to remove this prop completely
}
Updated dependencies [da47a0e, da47a0e, 9a120c8, 4cf75cb]:
7d771d8 Thanks @ardatan! - As Apollo suggests and uses in their implementation, we set the request timeout to 30 seconds for GraphOS uplinks#946 7d771d8 Thanks @ardatan! - dependencies updates:
@graphql-tools/executor@^1.4.7 ↗︎ (to dependencies)#950 c7ea2c5 Thanks @kroupacz! - Errors should not be swallowed when it is thrown from the shared root
Updated dependencies [c7ea2c5, 0af3485]:
#532 4e33933 Thanks @EmrysMyrddin! - dependencies updates:
@whatwg-node/promise-helpers@^1.3.0 ↗︎ (from ^1.2.5, in dependencies)Updated dependencies [4e33933, 4e33933, c9cd206, 4e33933, 4e33933, 7b86c09, dbfb0f7]:
#862 278618a Thanks @ardatan! - dependencies updates:
@whatwg-node/promise-helpers@^1.2.5 ↗︎ (from ^1.0.0, in dependencies)Updated dependencies [278618a, 278618a, 278618a, 278618a]:
#726 6334b2e Thanks @ardatan! - dependencies updates:
@whatwg-node/promise-helpers@^1.0.0 ↗︎ (to dependencies)#727 c54a080 Thanks @renovate! - dependencies updates:
@whatwg-node/disposablestack@^0.0.6 ↗︎ (from ^0.0.5, in dependencies)Updated dependencies [6334b2e, 6334b2e, c54a080, d949143, 661b103, 6334b2e, 6334b2e, 9c2f323, 2a54e85]:
#696 a289faa Thanks @ardatan! - dependencies updates:
@whatwg-node/fetch@^0.10.4 ↗︎ (from ^0.10.1, in dependencies)Updated dependencies [a289faa, 20d275c]:
2318393]:#620 d72209a Thanks @renovate! - dependencies updates:
@graphql-tools/utils@^10.8.1 ↗︎ (from ^10.7.0, in dependencies)Updated dependencies [d72209a, d72209a, d72209a, d72209a, 7146f8d, 7146f8d]:
#444 b52c9ba Thanks @ardatan! - Now SupergraphSchemaManager can be used in ApolloServer as gateway;
import { ApolloServer } from '@apollo/server';
import { SupergraphSchemaManager } from '@graphql-tools/federation';
const gateway = new SupergraphSchemaManager();
const apolloServer = new ApolloServer({
gateway,
});
And with the new onStitchedSchema option, you can manipulate the executable schema created from the supergraph.
The following example demonstrates how to use onStitchedSchema with applyMiddleware from graphql-middleware:
import { SupergraphSchemaManager } from '@graphql-tools/federation';
import { applyMiddleware } from 'graphql-middleware';
const logInput = async (resolve, root, args, context, info) => {
console.log(`1. logInput: ${JSON.stringify(args)}`);
const result = await resolve(root, args, context, info);
console.log(`5. logInput`);
return result;
};
const logResult = async (resolve, root, args, context, info) => {
console.log(`2. logResult`);
const result = await resolve(root, args, context, info);
console.log(`4. logResult: ${JSON.stringify(result)}`);
return result;
};
const gateway = new SupergraphSchemaManager({
onStitchedSchema: async (schema) => {
// Manipulate the schema
return applyMiddleware(schema, logInput, logResult);
},
});
#552 b0bc26b Thanks @ardatan! - Handle shared subscription root fields correctly
In case of conflicting subscription root fields coming from different subgraphs or different entry points(multiple keys), subscription was failing.
Updated dependencies [9144222]:
18682e6, e9f78cd]:#443 a625269 Thanks @ardatan! - In case of shared Mutation field in different subgraphs, choose the best option instead of choosing the last option just like we do in Query root fields
Updated dependencies [a625269, 14152f7]:
0591aa9 Thanks @ardatan! - Keep the custom directives(using @composeDirective) from the supergraph, in the unified schema served by the gateway should keep it.#387 3571399 Thanks @ardatan! - In case of shared root field on Mutation, it was batched incorrectly across subgraphs. But instead only one mutation should be called as mutations should not be parallel
Updated dependencies []:
#373 e606975 Thanks @ardatan! - dependencies updates:
@graphql-tools/utils@^10.7.0 ↗︎ (from ^10.6.2, in dependencies)Updated dependencies [e606975, e606975, e606975, e606975, 15975c2]:
#333 0d81307 Thanks @renovate! - dependencies updates:
@graphql-yoga/typed-event-target@^3.0.1 ↗︎ (from ^3.0.0, in dependencies)23b8987, 23b8987]:367b359]:#308 d747d4c Thanks @ardatan! - BREAKING CHANGES;
buildSubgraphSchema, use @apollo/subgraph instead.getSubschemaForFederationWithURLgetSubschemaForFederationWithTypeDefsgetSubschemaForFederationWithExecutorgetSubschemaForFederationWithSchemafederationSubschemaTransformerSupergraphSchemaManager is no longer an EventEmitter but EventTarget instead, and it emits a real Event object.SupergraphSchemaManager is now Disposable and it no longer stops based on Nodejs terminate events, so you should use using syntax.using manager = new SupergraphSchemaManager({ ... });
manager.addEventListener('error', (event: SupergraphSchemaManagerErrorEvent) => {
console.error(event.detail.error);
});
let schema: GraphQLSchema | null = null;
manager.addEventListener('schema', (event: SupergraphSchemaManagerSchemaEvent) => {
schema = event.detail.schema;
});
#308 d747d4c Thanks @ardatan! - dependencies updates:
@graphql-yoga/typed-event-target@^3.0.0 ↗︎ (to dependencies)@whatwg-node/disposablestack@^0.0.5 ↗︎ (to dependencies)@whatwg-node/events@^0.1.2 ↗︎ (to dependencies)#291 34d1224 Thanks @ardatan! - dependencies updates:
tslib@^2.8.1 ↗︎ (from ^2.4.0, in dependencies)Updated dependencies [34d1224, 34d1224, 34d1224, 34d1224]:
3f1a0fa]:#269 cdca511 Thanks @ardatan! - dependencies updates:
@graphql-tools/merge@^9.0.12 ↗︎ (from ^9.0.9, in dependencies)@graphql-tools/schema@^10.0.11 ↗︎ (from ^10.0.8, in dependencies)@graphql-tools/utils@^10.6.2 ↗︎ (from ^10.6.0, in dependencies)Updated dependencies [7df2215, cdca511, cdca511, cdca511, cdca511]:
9ce705c]:76642d8]:#231 7ca0ff3 Thanks @ardatan! - Avoid extensions and use `stitchingInfo` for provided fields
Updated dependencies [7ca0ff3]:
#205 2e0add3 Thanks @ardatan! - dependencies updates:
@whatwg-node/fetch@^0.10.1 ↗︎ (from ^0.10.0, in dependencies)#205 2e0add3 Thanks @ardatan! - Fix missing key fields in the nested queries
Updated dependencies [2e0add3, 2e0add3]:
#164 310613d Thanks @ardatan! - dependencies updates:
@graphql-tools/utils@^10.6.0 ↗︎ (from ^10.5.6, in dependencies)#185 f0b6921 Thanks @ardatan! - dependencies updates:
value-or-promise@^1.0.12 ↗︎ (from dependencies)#188 f71366d Thanks @ardatan! - dependencies updates:
value-or-promise@^1.0.12 ↗︎ (from dependencies)#199 b534288 Thanks @ardatan! - Logs are now easier to read, bigger results not do not create bigger outputs but instead they are all logged in a single line
Updated dependencies [310613d, 310613d, 9438e21, 310613d, f0b6921, f71366d, 310613d, f0b6921, f71366d, 9438e21, b534288, 697308d]:
725d5b7 Thanks @ardatan! - Fix regression on override type interface
Updated dependencies [725d5b7]:
f32cb2a]:73c621d, 19bc6a4]:d06afe3
Thanks @renovate! - dependencies updates:@whatwg-node/fetch@^0.10.0 ↗︎
(from ^0.9.17, in dependencies)d06afe3,
04d5cd7]:342e044
Thanks @ardatan! - Prevent extra queries to the same subgraph
multiple times on the same plan, and merge iterables correctly342e044]:#6619
e9906eb
Thanks @kroupacz! - Handle shared root field queries with aliases
Updated dependencies
[e9906eb]:
da1de08]:2bb2adb]:f470f49]:180f3f0
Thanks @ardatan! - Avoid extra calls if the keys are already
resolved
Updated dependencies
[180f3f0]:
4deac7f
Thanks @kroupacz! - If currentUnavailableSelectionSet.selections
is empty array then "query planning" will fail.b1e002f
Thanks @ardatan! - If required non-nullable key is null, do not send
it to the subgraph;
See optimizations.test.ts for more details.
#6586
8effad4
Thanks @ardatan! - Performance improvements on upstream request
execution
Updated dependencies
[8effad4]:
8a16b01]:4cdb462]:#6573
7e2938d
Thanks @ardatan! - When there are two services like below then the
following query senty, the gateway tries to fetch id as an extra field because it considers id
might be needed while this is not correct. This patch avoids any extra calls, and forwards the
query as is to the 2nd service.
query {
viewer {
booksContainer(input: $input) {
edges {
cursor
node {
source {
# Book(upc=)
upc
}
}
}
pageInfo {
endCursor
}
}
}
}
type Book @key(fields: "id") @key(fields: "upc") {
id: ID!
upc: ID!
}
type BookContainer { # the type that is used in a collection
id: ID!
# ... other stuff here
source: Book!
}
type Book @key(fields: "upc") {
upc: ID!
}
type Query {
viewer: Viewer
}
type Viewer {
booksContainer: BooksContainerResult
}
type BooksContainerResult {
edges: [BooksContainerEdge!]!
pageInfo: PageInfo!
}
type BooksContainerEdge {
node: BookContainer!
cursor: String!
}
type PageInfo {
endCursor: String
}
Updated dependencies
[7e2938d]:
dcb3e27,
cf2ce5e]:#6469
0e87805
Thanks @User!! - Handle merged selection sets in the computed fields;
When a selection set for a computed field needs to be merged, resolve that required selection set
fully then resolve the computed field. In the following case, the selection set for the author
field in the Post type is merged with the selection set for the authorId field in the
Comment type.
type Query {
feed: [Post!]!
}
type Post {
id: ID! @computed(selectionSet: "{ comments { authorId } }")
}
type Comment {
id: ID!
authorId: ID!
}
type User {
id: ID!
name: String!
}
type Post {
id: ID!
comments: [Comment!]!
}
type Comment {
id: ID!
}
Updated dependencies
[0e87805]:
#6441
52a69ed
Thanks @ardatan! - Filter errors as null in the projected key
If the key field has Error, do not send them to the subgraphs as objects but null.
#6437
3188051
Thanks @User, @()>),
@{, @{, @{,
@{, @{! - Fix the bug happens when a merged field
is a computed field requires another computed field requires a field from the initial subschema.
In the following test case, totalOrdersPrices needs userOrders which needs lastName from
initial Query.user. So the bug was skipping the dependencies of userOrders because it assumed
lastName already there by mistake.
const schema1 = makeExecutableSchema({
typeDefs: /* GraphQL */ `
type User {
id: ID!
firstName: String!
lastName: String!
address: String
}
type Query {
}
`,
resolvers: {
Query: {
=> {
return {
id: 1,
firstName: 'Jake',
lastName: 'Dawkins',
address: 'everywhere',
};
},
},
},
});
const schema2 = makeExecutableSchema({
typeDefs: /* GraphQL */ `
type UserOrder {
id: ID!
}
type User {
id: ID!
totalOrdersPrices: Int
aggregatedOrdersByStatus: Int
}
type Query {
userWithOrderDetails(userId: ID!, userOrderIds: [ID]): User
}
`,
resolvers: {
Query: {
userWithOrderDetails: (_root, { userId, userOrderIds }) => {
return {
id: userId,
userOrders: userOrderIds?.map((userOrderId: string) => ({ id: userOrderId })),
};
},
},
totalOrdersPrices(user) {
if (user.userOrders instanceof Error) {
return user.userOrders;
}
if (!user.userOrders) {
throw new Error('UserOrders is required');
}
return 0;
},
aggregatedOrdersByStatus(user) {
if (user.userOrders instanceof Error) {
return user.userOrders;
}
if (!user.userOrders) {
throw new Error('UserOrders is required');
}
return 1;
},
},
},
});
const schema3 = makeExecutableSchema({
typeDefs: /* GraphQL */ `
type User {
id: ID!
userOrders: [UserOrder!]
}
type UserOrder {
id: ID!
}
type Query {
userWithOrders(id: ID!, lastName: String): User
}
`,
resolvers: {
Query: {
userWithOrders: (_root, { id, lastName }) => {
return {
id,
lastName,
};
},
},
userOrders(user) {
if (!user.lastName) {
throw new Error('LastName is required');
}
return [
{
id: `${user.lastName}1`,
},
];
},
},
},
});
const stitchedSchema = stitchSchemas({
subschemas: [
{
schema: schema1,
},
{
schema: schema2,
merge: {
selectionSet: '{ id }',
fieldName: 'userWithOrderDetails',
args: ({ id, userOrders }: { id: string; userOrders: any[] }) => ({
userId: id,
userOrderIds: userOrders?.map?.(({ id }: { id: string }) => id),
}),
fields: {
totalOrdersPrices: {
selectionSet: '{ userOrders { id } }',
computed: true,
},
aggregatedOrdersByStatus: {
selectionSet: '{ userOrders { id } }',
computed: true,
},
},
},
},
},
{
schema: schema3,
merge: {
selectionSet: '{ id }',
fieldName: 'userWithOrders',
args: ({ id, lastName }: { id: string; lastName: string }) => ({
id,
lastName,
}),
fields: {
userOrders: {
selectionSet: '{ lastName }',
computed: true,
},
},
},
},
},
],
});
const res = await normalizedExecutor({
schema: stitchedSchema,
document: parse(/* GraphQL */ `
query User {
user {
aggregatedOrdersByStatus
totalOrdersPrices
}
}
`),
});
expect(res).toEqual({
data: {
aggregatedOrdersByStatus: 1,
totalOrdersPrices: 0,
},
},
});
Updated dependencies
[3188051]:
b8bf584
Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
directive handling in the extensions
Updated dependencies
[b8bf584]:
dbb0516
Thanks @ardatan! - If there are repeated computed fields like below,
project the data for the computed fields for each fields and merge them correctly. And if they
are array as in userOrders, merge them by respecting the order (the second one can have price
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 }")
}
#6403
3803897
Thanks @ardatan! - Cleanup extra fields, empty inline fragments and
duplicate __typename fields
Updated dependencies
[3803897]:
0d203ab
Thanks @ardatan! - Support @requires with arguments like
@requires(fields: "price(currency: 'USD')")63cab60
Thanks @ardatan! - Use type definition merger instead of
`concatAST` to merge type definitions for creating a subschema for Federation33e8146
Thanks @ardatan! - Fail on query planning phase if the query plan is
not successful before the actual execution
Updated dependencies
[33e8146]:
334d301
Thanks @EmrysMyrddin! - Expose the loaded supergrapth SDL in
the schema event167b47c
Thanks @ardatan! - New options to configure query batching and
batched delegation
{
batchingOptions: {
dataLoaderOptions: {
maxBatchSize: 10, // Limits the query batching
}
},
batchDelegateOptions: {
maxBatchSize: 10, // Limits the batch delegation
}
}
Learn more about these here; Batch Delegation Query Batching
d54b21a
Thanks @ardatan! - Do not apply type merging for non-resolvable
entities
Updated dependencies
[d54b21a,
d54b21a]:
#6355
c6d175b
Thanks @ardatan! - Handle errors coming from subgraphs correctly
when a root field is shared by different subgraphs
Query.foo, and subgraph B returns the data, ignore the
error and keep it for null fields.AggregateError then return them to the gateway
result.Updated dependencies
[8094c37,
97c88a0]:
#6293
3f301dc
Thanks @ardatan! - Do not use entryPoints for MergedTypeConfig
if there is only one
#6278
66c99d9
Thanks @ardatan! - Exclude @defer in the subgraph requests
Updated dependencies
[66c99d9,
3f301dc]:
#6267
d5dd794
Thanks @EmrysMyrddin! - Add delayInSeconds to the failure
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.
d5dd794
Thanks @EmrysMyrddin! - Fix Supergraph Manager Event Emitter
not calling every listener when at least one has been registered using once method.#6238
0f7059b
Thanks @ardatan! - Merge the elements of the lists if the root field
is shared across different subgraphs
type Query {
products: [Product] # If this field is returned by multiple subgraphs, the elements of the lists will be merged
}
Updated dependencies
[0f7059b]:
85c383f
Thanks @ardatan! - BREAKING CHANGES:getSubschemasFromSupergraphSdl has been removed in favor of the new
getStitchingOptionsFromSupergraphSdl, and it returns the options for stitchSchemas instead
of the map of subschemasonExecutor has been removed in favor of onSubschemaConfighttpExecutorOpts instead of onExecutordb29280
Thanks @EmrysMyrddin! - dependencies updates:@whatwg-node/fetch@^0.9.17 ↗︎
(to dependencies)#6194
7368829
Thanks @ardatan! - Handle interface objects in a different way
#6189
0134f7f
Thanks @ardatan! - Handle interface types with non-shared
implementations;
For example, you have the following services, where Node is implemented in both services, but
Foo and Bar are only implemented in one service. And when the gateway receives the following
query, it should be converted to this because Node is not implemented as Bar in Service 1
while implemented in Service 2.
Query conversion;
# Gateway request
query {
fooBar(id: "1") {
... on Node {
id
}
}
}
# Service 1 Request
query {
fooBar(id: "1") {
... on Foo {
id
}
... on Bar {
id
}
}
}
Services;
# Service 1
union FooBar = Foo | Bar
interface Node {
id: ID!
}
type Foo implements Node {
id: ID!
}
type Bar {
id: ID!
}
type Query {
fooBar(id: ID!): FooBar
}
# Service 2
interface Node {
id: ID!
}
type Foo implements Node {
id: ID!
}
type Bar implements Node {
id: ID!
}
#6187
dfccfbf
Thanks @ardatan! - Respect @provides to optimize the query plan
#6188
e10c13a
Thanks @ardatan! - If two different subschemas have the root field,
use the same field to resolve missing fields instead of applying a type merging in advance
Updated dependencies
[7368829,
e10c13a,
e10c13a,
dfccfbf,
0134f7f,
eec9d3d,
03a47b1,
e10c13a,
0827497]:
#6141
cd962c1
Thanks @ardatan! - When the gateway receives the query, now it
chooses the best root field if there is the same root field in different subgraphs. For example,
if there is node(id: ID!): Node in all subgraphs but one implements User and the other
implements Post, the gateway will choose the subgraph that implements User or Post based on
the query.
If there is a unresolvable interface field, it throws.
See this supergraph and the test query to see a real-life example
#6143
04d5431
Thanks @ardatan! - Implement interface objects support
Updated dependencies
[a83da08,
fc9c71f,
cd962c1]:
508ae6b
Thanks @ardatan! - Support overrides on interfaces See
packages/federation/test/fixtures/federation-compatibility/override-type-interface/supergraph.graphql
for more details#6126
680351e
Thanks @ardatan! - When there is a Node subschema, and others to
resolve the rest of the entities by using a union resolver as in Federation like below, it was
failing. This version fixes that issue.
query {
node(id: "1") {
id # Fetches from Node
... on User {
name # Fetches from User
}
}
}
type Query {
node(id: ID!): Node
}
interface Node {
id: ID!
}
type User implements Node {
id: ID!
}
type Post implements Node {
id: ID!
}
# User subschema
scalar _Any
type Query {
_entities(representations: [_Any!]!): [_Entity]!
}
union _Entity = User
interface Node {
id: ID!
}
type User implements Node {
id: ID!
name: String!
}
# Post subschema
scalar _Any
union _Entity = Post
type Query {
_entities(representations: [_Any!]!): [_Entity]!
}
interface Node {
id: ID!
}
type Post implements Node {
id: ID!
title: String!
}
Updated dependencies
[680351e]:
98b2795
Thanks @ardatan! - Improvements on unavailable field selection, and
key object projection
Updated dependencies
[98b2795]:
9238e14
Thanks @ardatan! - Improvements on field merging and extraction of
unavailable fields
Updated dependencies
[9238e14,
4ce3ffc]:
#6109
074fad4
Thanks @ardatan! - Show responses in debug logging with DEBUG env
var
Updated dependencies
[074fad4,
074fad4]:
#6091
9bca9e0
Thanks @User, @User! - If the gateway
receives a query with an overlapping fields for the subschema, it uses aliases to resolve it
correctly.
Let's say subschema A has the following schema;
type Query {
}
interface User {
id: ID!
name: String!
}
type Admin implements User {
id: ID!
name: String!
role: String!
}
type Customer implements User {
id: ID!
name: String
email: String
}
And let's say the gateway has the following schema instead;
type Query {
}
interface User {
id: ID!
name: String!
}
type Admin implements User {
id: ID!
name: String!
role: String!
}
type Customer implements User {
id: ID!
name: String!
email: String!
}
In this case, the following query is fine for the gateway but for the subschema, it's not;
query {
user {
... on Admin {
id
name # This is nullable in the subschema
role
}
... on Customer {
id
name # This is non-nullable in the subschema
email
}
}
}
So the subgraph will throw based on this rule OverlappingFieldsCanBeMerged
To avoid this, the gateway will use aliases to resolve the query correctly. The query will be transformed to the following;
query {
user {
... on Admin {
id
name # This is nullable in the subschema
role
}
... on Customer {
id
name: _nullable_name # This is non-nullable in the subschema
email
}
}
}
Updated dependencies
[9bca9e0,
9bca9e0,
243c353]:
107c021
Thanks @ardatan! - If an interface or scalar type is not annotated
for a subgraph explicitly, consider them as a shared type83c0af0
Thanks @enisdenjo! - dependencies updates:@graphql-tools/delegate@^10.0.3 ↗︎
(from ^10.0.1, in dependencies)@graphql-tools/executor-http@^1.0.8 ↗︎
(from ^1.0.6, in dependencies)@graphql-tools/merge@^9.0.1 ↗︎
(from ^9.0.0, in dependencies)@graphql-tools/schema@^10.0.2 ↗︎
(from ^10.0.0, in dependencies)@graphql-tools/stitch@^9.0.4 ↗︎
(from ^9.0.2, in dependencies)@graphql-tools/utils@^10.0.13 ↗︎
(from ^10.0.0, in dependencies)@graphql-tools/wrap@^10.0.1 ↗︎
(from ^10.0.0, in dependencies)83c0af0,
83c0af0,
83c0af0,
83c0af0,
83c0af0,
83c0af0,
83c0af0]:7583729
Thanks @ardatan! - Fix getSubschemaForFederationWithTypeDefs for
non-supergraph merging of subgraphsba062ff
Thanks @darren-west! - fix: buildSubgraphSchema with no entity
keys974df8a
Thanks @ardatan! - Debug logging & expose the subgraph schema
Updated dependencies
[b798b3b]:
250715a1
Thanks @ardatan! - Support extend type in subgraph SDL
250715a1
Thanks @ardatan! - Support supergraph with no join__type
directives on Query type
cda328c3
Thanks @ardatan! - Support for multiple key entrypoints for an
object, and avoid sending whole object if possible
Updated dependencies
[cda328c3]:
#5474
f31be313
Thanks @ardatan! - dependencies updates:
lodash.pick@^4.4.0 ↗︎
(from dependencies)#5474
f31be313
Thanks @ardatan! - Optimizations for federation
Updated dependencies
[f31be313]:
#5468
de9e8a67
Thanks @ardatan! - dependencies updates:
lodash.pick@^4.4.0 ↗︎
(to dependencies)#5468
de9e8a67
Thanks @ardatan! - Reduce the number of upstream requests
944a68e8,
8fba6cc1,
944a68e8,
944a68e8,
944a68e8]:24c13616
Thanks @ardatan! - dependencies updates:@graphql-tools/executor-http@^0.1.9 ↗︎
(from ^0.0.7, in dependencies)#5212
0cd9e8c4
Thanks @ardatan! - dependencies updates:
@graphql-tools/delegate@^9.0.19 ↗︎
(from 9.0.19, in dependencies)@graphql-tools/merge@^8.3.16 ↗︎
(from 8.3.16, in dependencies)@graphql-tools/schema@^9.0.14 ↗︎
(from 9.0.14, in dependencies)@graphql-tools/wrap@^9.2.20 ↗︎
(from 9.2.20, in dependencies)@graphql-tools/utils@^9.1.3 ↗︎
(from 9.1.3, in dependencies)@graphql-tools/executor-http@^0.0.7 ↗︎
(from 0.0.7, in dependencies)@graphql-tools/stitch@^8.7.34 ↗︎
(from 8.7.34, in dependencies)value-or-promise@^1.0.12 ↗︎ (to
dependencies)Updated dependencies
[8e80b689]: