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.
Hi, I found a small issue, related to the default behavior of graphql. Here is an explanation of this issue:
Explanation
Let's make a test open extension fill
Set endpoint
field with correct graphql endpoint and cicck to button. In this case extension will send request like the next:We see only one field
query
. Let's make the next, copy body of this query to graphiql explorer and clickExecute Query
button (don't forget delete \n symbols). In this case, extension will send the next parameters:Most important difference between these parameters is
operationName
parameter. Our backend uses this parameter and other backend's could use too.To avoid this issue I created this PR.
Also, I don't want to create an additional extension in google store and increase confusing, because I created this PR.