Alex Genco

Just wanted to revive this conversation, as it would be a huge win for my team right now. Would it be helpful to make the `@export` directive be explicit about...

Another thought: My team's current requirements could probably be satisfied in a single operation with multiple mutations inside it, rather than multiple operations. This could potentially simplify the export variable...

@cmonty I think you basically have to inline all inputs down to the level of the exported variable, but anything deeper you could still include as an operation variable. So...

>Update handling of g:ruby_host_prog, so it can point to ruby >(Nvim 0.12) Remove old rplugin-related code Is there anything to do for these in this repo? These seem like changes...

> if the user was null, would $commentIds be null or the empty list? This is a good question... Does anyone know what happens in Sangria in this scenario? (first...

> This seems like it could open a number of issues for client libraries, particularly strongly typed ones. What kinds of issues are you thinking? Passing exported variables into `@skip`...

Thanks @IvanGoncharov this is very helpful. We will try this approach on our end and see what comes out of it.

Hey sorry for the radio silence here. We finally got around to the suggestion from @IvanGoncharov and have posted the result on our docs: ~~https://graphql.braintreepayments.com/guides/sequence_requests/~~. Would be interested to hear...

Thanks for that, @benjie , I missed that part of the hotchocolate docs, and assumed they had implemented batching only with the multiple-operation approach, which we have been trying to...

Will do. But we are generally taking a minimalist approach to those types of edge cases, and leaning as heavily on the default type checking as possible.