From a77dce25ab2224091fda969495c3e86ad09447e3 Mon Sep 17 00:00:00 2001 From: Maria Elisabeth Schreiber Date: Mon, 21 Oct 2024 10:20:51 -0600 Subject: [PATCH] docs: fix broken links (#3173) Update links --- docs/source/entities/contribute-fields.mdx | 2 +- docs/source/entities/handling-n-plus-one.mdx | 2 +- docs/source/federated-schemas/federated-directives.mdx | 2 +- docs/source/federation-2/new-in-federation-2.mdx | 2 +- docs/source/query-plans.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/source/entities/contribute-fields.mdx b/docs/source/entities/contribute-fields.mdx index 83e81df83..6ad80bbdd 100644 --- a/docs/source/entities/contribute-fields.mdx +++ b/docs/source/entities/contribute-fields.mdx @@ -35,7 +35,7 @@ By default, each subgraph must contribute different fields, with the important e If multiple subgraphs attempt to contribute the same field, a composition error occurs. To override this default behavior, see [Resolving another subgraph's field](/graphos/schema-design/federated-schemas/entities/resolve-another-subgraphs-fields). -Each subgraph that contributes fields to an entity must [define a reference resolver](/graphos/get-started/guides/federate-schemas/#2-define-a-reference-resolver) for that entity. +Each subgraph that contributes fields to an entity must [define a reference resolver](/graphos/schema-design/federated-schemas/entities/intro/#2-define-a-reference-resolver) for that entity. ## Contributing computed entity fields diff --git a/docs/source/entities/handling-n-plus-one.mdx b/docs/source/entities/handling-n-plus-one.mdx index 091d22146..a658ad246 100644 --- a/docs/source/entities/handling-n-plus-one.mdx +++ b/docs/source/entities/handling-n-plus-one.mdx @@ -163,7 +163,7 @@ QueryPlan { Most subgraph implementations (including [`@apollo/subgraph`](/apollo-server/using-federation/api/apollo-subgraph/)) don't write the [`Query._entities` resolver](/graphos/reference/federation/subgraph-specific-fields/#query_entities) directly. -Instead, they use the [reference resolver API](/graphos/get-started/guides/federate-schemas/#2-define-a-reference-resolver) for resolving an individual entity reference: +Instead, they use the [reference resolver API](/graphos/schema-design/federated-schemas/entities/intro/#2-define-a-reference-resolver) for resolving an individual entity reference: ```js const resolvers = { diff --git a/docs/source/federated-schemas/federated-directives.mdx b/docs/source/federated-schemas/federated-directives.mdx index a3855889d..763eabe69 100644 --- a/docs/source/federated-schemas/federated-directives.mdx +++ b/docs/source/federated-schemas/federated-directives.mdx @@ -185,7 +185,7 @@ See also [Advanced `@key`s](/graphos/schema-design/federated-schemas/entities/de -If `false`, indicates to the router that this subgraph doesn't define a [reference resolver](/graphos/get-started/guides/federate-schemas#2-define-a-reference-resolver) for this entity. This means that router query plans can't "jump to" this subgraph to resolve fields that aren't defined in another subgraph. +If `false`, indicates to the router that this subgraph doesn't define a [reference resolver](/graphos/schema-design/federated-schemas/entities/intro/#2-define-a-reference-resolver) for this entity. This means that router query plans can't "jump to" this subgraph to resolve fields that aren't defined in another subgraph. Most commonly, you set this to `false` when [referencing an entity without contributing fields](/graphos/schema-design/federated-schemas/entities/contribute-fields#referencing-an-entity-without-contributing-fields). diff --git a/docs/source/federation-2/new-in-federation-2.mdx b/docs/source/federation-2/new-in-federation-2.mdx index 012e2d208..9974e1cee 100644 --- a/docs/source/federation-2/new-in-federation-2.mdx +++ b/docs/source/federation-2/new-in-federation-2.mdx @@ -187,7 +187,7 @@ For more information, see [Resolving another subgraph's field](/graphos/schema-d ### Changes to `@key` -Federation 2 adds a new optional argument to the `@key` directive: `resolvable`. You can set this argument to `false` to indicate that a particular subgraph doesn't define a [reference resolver](/graphos/get-started/guides/federate-schemas#2-define-a-reference-resolver) for that entity. +Federation 2 adds a new optional argument to the `@key` directive: `resolvable`. You can set this argument to `false` to indicate that a particular subgraph doesn't define a [reference resolver](/graphos/schema-design/federated-schemas/entities/intro/#2-define-a-reference-resolver) for that entity. For example: diff --git a/docs/source/query-plans.mdx b/docs/source/query-plans.mdx index 7d6340912..b07a212d0 100644 --- a/docs/source/query-plans.mdx +++ b/docs/source/query-plans.mdx @@ -419,7 +419,7 @@ Flatten(path: "hotels.@") { Instead of containing a GraphQL operation, this `Fetch` node contains two GraphQL fragments, separated by `=>`. -- The first fragment is a representation of the entity being resolved (in this case, `Hotel`). [Learn more about entity representations](/graphos/get-started/guides/federate-schemas/#2-define-a-reference-resolver). +- The first fragment is a representation of the entity being resolved (in this case, `Hotel`). [Learn more about entity representations](/graphos/schema-design/federated-schemas/entities/intro/#2-define-a-reference-resolver). - The second fragment contains the entity fields and subfields that the router needs the subgraph to resolve (in this case, `Hotel.reviews` and `Review.rating`). When the router sees this special `Fetch` syntax, it knows to query a subgraph's [`Query._entities` field](/graphos/reference/federation/subgraph-specific-fields/#query_entities). This field is what enables a subgraph to provide direct access to any available fields of an entity.