Matias A.
Matias A.
Hello @bwplotka, not sure if the version matters, but what I'm seeing is that if I use `bingo get` to update a dependency after I've updated my version of `go`...
I set the following error presenter in my code to solve this issue for now: ```golang server.SetErrorPresenter(func(ctx context.Context, e error) *gqlerror.Error { err := graphql.DefaultErrorPresenter(ctx, e) var extendedErr interface{ Extensions()...
@DenisNeustroev since in your case the upstream resolver (i.e. `Orders`) knows how to construct the batch query for the downstream resolver (i.e. `Client`) you can still get only two requests...
@reem is there anything outstanding stoping this issue from being resolved / closed?
Is there anything holding this change back?
Hi @kivutar, thanks for bringing this up. I believe this is an issue with the version of [apollographql/subscriptions-transport-ws](https://github.com/apollographql/subscriptions-transport-ws), which is the client this example uses to enable graphiql to work...
Hi @smithaitufe, this issue was reported in the corresponding library [here](https://github.com/apollographql/GraphiQL-Subscriptions-Fetcher/issues/15) and I added a [pull-request](https://github.com/apollographql/GraphiQL-Subscriptions-Fetcher/pull/19) to fix it, but it hasn't been merged. In the mean time you can...
@actuallymentor thoughts? #312-#300 is very annoying.
@Piero94 I haven't had much luck with @actuallymentor - even tried him on x.com - would love to see this merged.