From 0afd63a5c384f0c8e0914a2568dec92e2dca9c00 Mon Sep 17 00:00:00 2001 From: deterclosed <164524498+deterclosed@users.noreply.github.com> Date: Sat, 23 Mar 2024 19:43:23 +0800 Subject: [PATCH] chore: remove repetitive words (#2976) Signed-off-by: deterclosed --- CHANGELOG.md | 2 +- docs/content/reference/resolvers.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a9311c29f28..acea9f11d79 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3573,7 +3573,7 @@ when generating next the context was captured there. Which means later when the returned function from DispatchOperation is called. The responseContext which accumulates the errors is the -tempResponseContext which we no longer have access to to read the errors +tempResponseContext which we no longer have access to read the errors out of it. Instead add a context to next() so that it can be passed through and diff --git a/docs/content/reference/resolvers.md b/docs/content/reference/resolvers.md index d4a11570d3f..3400e5e2851 100644 --- a/docs/content/reference/resolvers.md +++ b/docs/content/reference/resolvers.md @@ -94,7 +94,7 @@ context is required, the model method will also be run in parallel. ## Bind when the field names do not match -There are two ways you can bind to fields when the the Go struct and the graphQL type do not match. +There are two ways you can bind to fields when the Go struct and the graphQL type do not match. The first way is you can bind resolvers to a struct based off of struct tags like the following: