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.

Sign up for GitHub

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

Jump to bottom

chore: remove repetitive words #2976

Merged
merged 1 commit into from
Mar 23, 2024
Merged

chore: remove repetitive words #2976

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
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
View file
Open in desktop
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