After latest updates, it started getting error as below
GraphQL Request parameter "operation" must be string, but got (empty string)
Version 1.4.1
Last Updated : December 23, 2019
Sorry this isn't descriptive enough. You should use the issue template. Where do you get the error? What platform are you using?
Sorry for inconvenience. I am using Ubuntu 19.04
It happens on both chrome Version 78.0.3904.108 (Official Build) (64-bit) and firefox 71.0 (64-bit).
This happens on both Query and Mutations. It was working ok before today's version update.
for example this
````
query{
event(id: 64){
id
type
title
}
}
Do you get the error in the console? Did you get an error alert in the app? Are you using the browser extensions or the web app?
Can you set the name of your query like query somename {...}?
I am using browser extension
Tried with name but it gives same error
query something {
event(id: 64){
id
type
title
}
}
It gives error in console as well as in output screen
error: Object { errors: (1) […] }
​headers: Object { normalizedNames: Map(0), lazyUpdate: null, lazyInit: lazyInit() }
​message: "Http failure response for http://localhost/graphql: 400 Bad Request"
​name: "HttpErrorResponse"
​ok: false
​status: 400
​statusText: "Bad Request"
url: "http://localhost/graphql"
It passes operationName to blank
operationName: ""
query: "query{↵ event(id: 64){↵ id↵ type↵ title↵ comment↵ }↵}"
variables: {}
Okay one more thing. Try adding a second query (that is, you should have two queries in your request with names) and sending.
@imolorhe yep, it works with two queries
@imolorhe oh, it works for queries, but doesn't work for Reload Docs, because getting docks is one query:
query: "query IntrospectionQuery {...}"
variables: {}
operationName: ""
Right. So I understand the issue now sufficiently. Can you try with the Firefox add-on?
@imolorhe it works with 2 named queries, introspection query not working with both Chrome and Firefox.
Thanks. Will push a new release with the fix today. Sorry for the inconvenience.
Closed in 1868419c17fe0270c69582ec5110c32c73cb61b5. Would be fixed in v2.4.2.
Most helpful comment
Closed in 1868419c17fe0270c69582ec5110c32c73cb61b5. Would be fixed in v2.4.2.