graphql: add nil checks in Block resolver methods #33225
+3
−0
Conversation
This file contains hidden or 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
| if err != nil { | ||
| return nil, err | ||
| } | ||
| if b.header == nil { |
Member
There was a problem hiding this comment.
This change makes all the following changes unnecessary
Contributor
Author
There was a problem hiding this comment.
Hi @MariusVanDerWijden, updated, pleasee take a look, thanks.
rizkyikiw42
force-pushed
the
graphql-nil-checks
branch
from
bd1053c to
e4c011b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add nil checks for header and block in Block resolver methods to prevent panic when querying non-existent blocks.