graphql issues

Allow [][2]interface{} (ordered map) along with struct in query and mutation #80

1

See #80 for details

Allow building mutations from maps instead of structs

Suppose I can create user like this ```GraphQL mutation($login: String!) { createUser(login: $login) { login } } variables { "login": "grihabor" } ``` Now I'd like to create multiple users...

grihabor

define a customized error type to carry status code and body

as a user, I want to know status code directly instead of parsing error text, just incase error text got changed one day Signed-off-by: Leslie Qi Wang

leslie-qiwa

better error message or different behavior when expecting slice of structs, but have single struct

3

From https://github.com/shurcooL/graphql/issues/45#issuecomment-527848376: > this package should do something better in this situation. Either the error message needs to be improved, or maybe it could unmarshal just the first book and...

dmitshur

API decision

NeedsInvestigation

Using alternative rest clients

Hello, I was wondering if its possible to use alternative HTTP clients or how much work it would be to support this. For example i'm looking to add retry &...

rocktavious

Allow providing a custom request factory

3

This PR allows customizing the requests sent for APIs that require additional headers. Replace #47, #48, #49, https://github.com/shurcooL/graphql/pull/64, #68. This is not the most beautiful solution but offers the highest...

andig

Add variadic RequestOption to Query and Mutate

3

Fixes https://github.com/shurcooL/graphql/issues/28. I saw various solutions in https://github.com/shurcooL/graphql/issues/28, especially this one: https://github.com/shurcooL/graphql/issues/28#issuecomment-485226864. I decided to take the variadic options approach because: 1) It's backwards compatible 2) Easy to build on...

iheanyi