Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Update router terminology" #11892

Merged
merged 1 commit into from
Jun 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/source/api/link/persisted-queries.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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)
- [GraphOS Router](/router) (v1.25.0+)
- [Apollo 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 Core:
You can use APQ with the following versions of Apollo Client Web, Apollo Server, and Apollo Router:
- Apollo Client Web (v3.2.0+)
- [Apollo Server](/apollo-server/) (v1.0.0+)
- [Apollo Router Core](/router) (v0.1.0+)
- [Apollo Router](/router) (v0.1.0+)

> **Note:** You can use _either_ Apollo Server _or_ Apollo Router Core for APQs. They don't need to be used together.
> **Note:** You can use _either_ Apollo Server _or_ Apollo Router 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 [GraphOS Router](/router/) can check incoming requests against.
An operation manifest acts as a safelist the [Apollo 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:
Expand Down
2 changes: 1 addition & 1 deletion docs/source/data/defer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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 [GraphOS 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 [Apollo Router](/router/executing-operations/defer-support/) and is compatible with all [federation-compatible subgraph libraries](/federation/building-supergraphs/supported-subgraphs/).

## Example

Expand Down
Loading