fix: add more details when graphql request is invalid #2306
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
Signed-off-by: Benjamin Coenen <5719034+bnjjj@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
o0Ignition0o
approved these changes
Dec 22, 2022
Geal
approved these changes
Dec 22, 2022
abernix
reviewed
Dec 22, 2022
…w how the whole graphql response looks like.
o0Ignition0o
force-pushed
the
bnjjj/fix_2301
branch
from
28a1cff
to
019b4ac
Compare
Merged
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.
close #2301
here is the new error you'll receive:
{ "message": "Invalid GraphQL request", "extensions": { "details": "failed to deserialize the request body into JSON: invalid type: string \"null\", expected a map at line 1 column 100", "code": "INVALID_GRAPHQL_REQUEST" } }