-
Notifications
You must be signed in to change notification settings - Fork 14
Passing query as JSON (for variables, etc.) seems broken #24
Comments
Probably checking Content-Type (either |
hey @uebayasi ,
Meaning, if you send a JSON object ( The code that follows reads The reason this handler is implemented in |
Thanks for the quick reply! Now I see the problem;
This is google-cloud-sdk 132.0.0 (2016/10/19). |
In requests.py there's this code:
So basically |
This is part of the webob 1.2.3 library that webapp2 depends on |
I see that webapp2-2.5.1 and webob-1.2.3 are used (imported) here. I can't figure out why those inherited methods are called. I'll try to investigate this later, but I can't promise. Feeling like Python not being my friend. :( |
For some reasons the Obviously this problem is not relevant to graphene-gae. It is either google-gcloud-sdk or python2.7 or my local environment causing the oddity. Feel free to close this issue. Fortunately my project is not really started yet. I'm considering to switch to something and stay away from Python if possible... :( |
I just ran into this issue on a fresh install of Google Cloud SDK. It seems that libraries:
- name: webob
version: 1.2.3
- name: webapp2
version: 2.5.2 |
I'm very new to this GraphQL world but my understanding of GraphQL is that, in order to pass
variables
oroperation_name
in addition toquery
, the body of POST has to be encoded in JSON. A GraphQL query HTML body, with a pair ofquery
andvariables
, would look like:This does not seem to work with graphene-gae. I put many logging.warn()'s in
_get_grapl_params()
but could not understand the intent. If the said assumption that GraphQL query body is either raw GraphQL or JSON, this_get_grapl_params()
would look like:(I even have no idea why this handler has to be implemented in graphene-gae, not graphene.)
I'm trying to fix this myself, but I'm slow; new to Python, new to GraphQL, new to Web world. Feel free to beat me. ;)
The text was updated successfully, but these errors were encountered: