John McCaulley

> Can you explain more about what this is. I have no idea on what this means at all. Sorry, which part? This about covers what I mean with batching...

As I write/think about this pr more it seems like adding the execution id to the execution input, along with creating it earlier in the execution life cycle would allow...

I still need to add some decent test cases dedicated to this use case and clean up the code a little but this seems promising so far: https://github.com/graphql-java/graphql-java/pull/1539

@bbakerman I've added two working test cases, but I'm not completely happy with the way it has turned out. A cleaner solution would be along the lines of allowing multiple...

> However as I understand it they run them one after the other and combine them into the a series of results. eg a map like This is similar to...

Sorry, I think I need to be more explicit here about operations as we are not necessarily talking about the same thing. I don't mean operations within a single document,...

Here is the pr to add the id to the input: https://github.com/graphql-java/graphql-java/pull/1550 I'm hesitant to spend much time working on a "batched" method without any indication that it would be...

Not sure if this will be helpful, but we had a number of chained calls to data loaders. The issue is that the dispatching instrumentation assumes one load per level...

I don't think I see how that would help. I think the ideal solution would be to somehow make the framework aware of the number of dispatches required, as with...

After a bit of Googling I found some stack overflow posts about needing to implement a custom view to have more than three actions in Android. They are a bit...