From 1aca223b8da3fe02bbd38379d6a211844e0b40bb Mon Sep 17 00:00:00 2001 From: Maria Elisabeth Schreiber Date: Wed, 12 Jun 2024 11:48:12 -0600 Subject: [PATCH] Update router terminology (#11885) --- docs/source/api/link/persisted-queries.mdx | 10 +++++----- docs/source/data/defer.mdx | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/source/api/link/persisted-queries.mdx b/docs/source/api/link/persisted-queries.mdx index e2b4a35da86..4d71bfbf25d 100644 --- a/docs/source/api/link/persisted-queries.mdx +++ b/docs/source/api/link/persisted-queries.mdx @@ -31,21 +31,21 @@ Using persisted queries for safelisting has the following requirements: - Apollo Client Web (v3.7.0+) - The [`@apollo/generate-persisted-query-manifest` package](https://www.npmjs.com/package/@apollo/generate-persisted-query-manifest) - The [`@apollo/persisted-query-lists` package](https://www.npmjs.com/package/@apollo/persisted-query-lists) -- [Apollo Router](/router) (v1.25.0+) +- [GraphOS Router](/router) (v1.25.0+) - [GraphOS Enterprise plan](/graphos/enterprise/) -You can use APQ with the following versions of Apollo Client Web, Apollo Server, and Apollo Router: +You can use APQ with the following versions of Apollo Client Web, Apollo Server, and Apollo Router Core: - Apollo Client Web (v3.2.0+) - [Apollo Server](/apollo-server/) (v1.0.0+) -- [Apollo Router](/router) (v0.1.0+) +- [Apollo Router Core](/router) (v0.1.0+) -> **Note:** You can use _either_ Apollo Server _or_ Apollo Router for APQs. They don't need to be used together. +> **Note:** You can use _either_ Apollo Server _or_ Apollo Router Core for APQs. They don't need to be used together. ## 1. Generate operation manifests > **This step is only required for persisted queries, not APQ.** -An operation manifest acts as a safelist the [Apollo Router](/router/) can check incoming requests against. +An operation manifest acts as a safelist the [GraphOS Router](/router/) can check incoming requests against. You can generate the manifest using the [`@apollo/generate-persisted-query-manifest`](https://www.npmjs.com/package/@apollo/generate-persisted-query-manifest) package: 1. Install the [`@apollo/generate-persisted-query-manifest`](https://www.npmjs.com/package/@apollo/generate-persisted-query-manifest) package as a dev dependency: diff --git a/docs/source/data/defer.mdx b/docs/source/data/defer.mdx index 908ada61c6b..6b43736590b 100644 --- a/docs/source/data/defer.mdx +++ b/docs/source/data/defer.mdx @@ -7,7 +7,7 @@ description: Receive query response data incrementally Beginning with version `3.7.0`, Apollo Client provides preview support for [the `@defer` directive](https://github.com/graphql/graphql-wg/blob/main/rfcs/DeferStream.md). This directive enables your queries to receive data for specific fields _incrementally_, instead of receiving all field data at the same time. This is helpful whenever some fields in a query take much longer to resolve than others. -> For a query to defer fields successfully, the queried endpoint must _also_ support the `@defer` directive. Entity-based `@defer` support is also at the General Availability stage in [Apollo Router](/router/executing-operations/defer-support/) and is compatible with all [federation-compatible subgraph libraries](/federation/building-supergraphs/supported-subgraphs/). +> For a query to defer fields successfully, the queried endpoint must _also_ support the `@defer` directive. Entity-based `@defer` support is also at the General Availability stage in [GraphOS Router](/router/executing-operations/defer-support/) and is compatible with all [federation-compatible subgraph libraries](/federation/building-supergraphs/supported-subgraphs/). ## Example