From cd80dfb54bd2a43d890f15bafd1aeb18984a61f7 Mon Sep 17 00:00:00 2001 From: Mandi Wise Date: Mon, 25 Nov 2024 09:45:20 -0700 Subject: [PATCH 1/2] Fix links that are broken until other pages ship. --- src/pages/learn/security.mdx | 2 +- src/pages/learn/serving-over-http.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/learn/security.mdx b/src/pages/learn/security.mdx index c3945b744d..77d5764fb7 100644 --- a/src/pages/learn/security.mdx +++ b/src/pages/learn/security.mdx @@ -77,7 +77,7 @@ query { } ``` -Even when [the N+1 problem](/learn/performance/#the-n1-problem) has been remediated through batched requests to underlying data sources, overly nested fields may still place excessive load on server resources and impact API performance. +Even when the N+1 problem has been remediated through batched requests to underlying data sources, overly nested fields may still place excessive load on server resources and impact API performance. For this reason, it's a good idea to limit the maximum depth of fields that a single operation can have. Many GraphQL implementations expose configuration options that allow you to specify a maximum depth for a GraphQL document and return an error to the client if a request exceeds this limit before execution begins. diff --git a/src/pages/learn/serving-over-http.mdx b/src/pages/learn/serving-over-http.mdx index 22021696cf..3625540e73 100644 --- a/src/pages/learn/serving-over-http.mdx +++ b/src/pages/learn/serving-over-http.mdx @@ -6,7 +6,7 @@ import { Callout } from "nextra/components" The GraphQL specification doesn't require paricular client-server protocols when sending API requests and responses, but HTTP is the most common choice because of its ubiquity. On this page, we'll review some key guidelines to follow when setting up a GraphQL server to operate over HTTP. -Note that the guidelines that follow only apply to stateless query and mutation operations. Visit the [Subscriptions page](/learn/subscriptions) for more information on transport protocols that commonly support these requests. +Note that the guidelines that follow only apply to stateless query and mutation operations. The recommendations on this page align with the detailed [GraphQL-over-HTTP specification](https://graphql.github.io/graphql-over-http/draft/) currently in development. Though not yet finalized, this draft specification acts as a single source of truth for GraphQL client and library maintainers, detailing how to expose and consume a GraphQL API using an HTTP transport. Unlike the language specification, adherence is not mandatory, but most implementations are moving towards these standards to maximize interoperability. From 3d3497e50c9c2516deea0059a6fccebca08932c7 Mon Sep 17 00:00:00 2001 From: Benjie Date: Mon, 25 Nov 2024 16:54:08 +0000 Subject: [PATCH 2/2] Discard changes to src/pages/learn/serving-over-http.mdx --- src/pages/learn/serving-over-http.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/learn/serving-over-http.mdx b/src/pages/learn/serving-over-http.mdx index 3625540e73..22021696cf 100644 --- a/src/pages/learn/serving-over-http.mdx +++ b/src/pages/learn/serving-over-http.mdx @@ -6,7 +6,7 @@ import { Callout } from "nextra/components" The GraphQL specification doesn't require paricular client-server protocols when sending API requests and responses, but HTTP is the most common choice because of its ubiquity. On this page, we'll review some key guidelines to follow when setting up a GraphQL server to operate over HTTP. -Note that the guidelines that follow only apply to stateless query and mutation operations. +Note that the guidelines that follow only apply to stateless query and mutation operations. Visit the [Subscriptions page](/learn/subscriptions) for more information on transport protocols that commonly support these requests. The recommendations on this page align with the detailed [GraphQL-over-HTTP specification](https://graphql.github.io/graphql-over-http/draft/) currently in development. Though not yet finalized, this draft specification acts as a single source of truth for GraphQL client and library maintainers, detailing how to expose and consume a GraphQL API using an HTTP transport. Unlike the language specification, adherence is not mandatory, but most implementations are moving towards these standards to maximize interoperability.