Closed flexzuu closed 6 years ago
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 https://github.com/machinebox/graphql/pull/15.
Pull master, there’s an official way to do that now too.
On 24 May 2018, at 19:49, Kamus Hadenes notifications@github.com 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 https://github.com/machinebox/graphql/issues/12#issuecomment-391820736, 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