-
Notifications
You must be signed in to change notification settings - Fork 44
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
fix: Handle errors generated in fields thunk #66
Merged
AndrewSisley
merged 3 commits into
develop
from
sisley/fix/I53-error-handling-in-fields-thunk-updated-fork
Dec 1, 2021
Merged
fix: Handle errors generated in fields thunk #66
AndrewSisley
merged 3 commits into
develop
from
sisley/fix/I53-error-handling-in-fields-thunk-updated-fork
Dec 1, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndrewSisley
added
bug
Something isn't working
area/schema
Related to the schema system
labels
Nov 30, 2021
Merged the updates on the sourcenetwork/graphql-go fork. Does anything need to change here (ie go.mod stuff) before merging? |
nvm, I see you already marked that as an outstanding task. Ill let you take care of it 👍, ping me if/when another review is needed |
jsimnz
approved these changes
Nov 30, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
AndrewSisley
force-pushed
the
sisley/fix/I53-error-handling-in-fields-thunk-updated-fork
branch
from
December 1, 2021 13:40
796c955
to
998be84
Compare
AndrewSisley
deleted the
sisley/fix/I53-error-handling-in-fields-thunk-updated-fork
branch
December 1, 2021 13:43
Closed
shahzadlone
pushed a commit
to shahzadlone/defradb
that referenced
this pull request
Feb 23, 2024
* Resolve fields in ResolveTypes function * Include type name in type missing error * Handle errors occuring during fields thunk resolution
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #53
The new version of the fork (in review sourcenetwork/graphql-go#2) stores errors from the thunk onto
object.err
(accessed publicly viaobject.Errors()
.To do before merge:
develop
branch