-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send query and variables in json body #12
Comments
OK so this is definitely worth changing then? |
yeah i think we should be agnostic how the server accepts it and add default implementations for the most common ones. |
Having problems on interacting with https://github.com/graphql-go/graphql because of this. |
What happens if you're submitting files? The body has to be a multipart, and can't be JSON? |
@matryer APIs like Graphcool have a separate API endpoint for submitting files (with multipart) - https://www.graph.cool/docs/reference/graphql-api/file-management-eer4wiang0 |
Please update and try again following #15. |
Pull master, there’s an official way to do that now too.
… On 24 May 2018, at 19:49, Kamus Hadenes ***@***.***> wrote:
Quick hack on https://github.com/kamushadenes/graphql <https://github.com/kamushadenes/graphql> got me going by implementing RunJSON()
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGNG4aBIjP25kfLrbcRKbvymi9GvLJuks5t1wDHgaJpZM4SvL_Y>.
|
@flexzuu this is fixed - please confirm? |
Closing assuming this is fixed. |
I think the issues #7 and #11 are both related to the the client sending data and variables as FormDataContentType but most server implementations expect them as application json in body like
The text was updated successfully, but these errors were encountered: