Variables field sent as [object Object] in GET requests

[macalinao]

My "Query Variables" is being sent as an [object Object]. There is probably a .toString call where there should really be a JSON.stringify.

[asiandrummer]

@macalinao Are you unable to execute a query? I think we've decided to send a JSON object instead of JSON string a while ago.

[macalinao]

Yes. What do you mean by sending a JSON object instead of JSON string?

[asiandrummer]

@macalinao oh sorry - I meant we had a discussion in #168 to change passing in variables in JSON object instead of string.

[macalinao]

ah, well it shouldn't be sending [object Object] should it? Or is it actually sending a JSON string and Chrome dev tools is showing some other representation?

[jborden]

I can confirm I am having this same problem with Query Variables. It seems to be isolated to the HTTP GET method calls. HTTP POST calls will gladly pass on the proper Query Variables in the request body, but for HTTP GET method calls the query is passed on with the parameters while the variables are just a string "[object Object]".

[wincent]

Can I get some clarification here on how to repro this exactly?

[jeroenbe]

I'm having the same issue:
I'm using the electron app to query a neo4j db with graphql (if you want to go through the hassle: neo4j-graphql).

When inspecting the requests with charles and copying them as a cURL request I noticed &variables\=%5Bobject%20Object%5D (-> [object Object]) at the end of my request. When no variables are given the ending looks like: &variables=null. When replacing the values with an encoded object, everything goes fine. Effectively ruling out the server as the culprit.

I understand there's a lot of indirect stuff going on in tracing my issue, but I'm fairly confident it's the same one as described above.

[macalinao]

@wincent to reproduce, send a GraphQL request via GET with some variables.

The above comment by @jeroenbe describes the issue pretty well.