Skip to content

Commit

Permalink
chore: remove repetitive words (#2976)
Browse files Browse the repository at this point in the history
Signed-off-by: deterclosed <fliter@outlook.com>
  • Loading branch information
deterclosed committed Mar 23, 2024
1 parent ee526b0 commit 0afd63a
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/content/reference/resolvers.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down

0 comments on commit 0afd63a

Please sign in to comment.