Shane Krueger
Shane Krueger
Then `opts.Variables = request.Variables;`
@sungam3r Please review and provide thoughts. I am in the middle of rewriting SubscriptionExecutionStrategy and ran into so many issues with the existing codebase that I wanted you to look...
Please note that I will be writing extensive tests for the new SubscriptionExecutionStrategy implementation(s). Whatever we decide, it will be rock solid.
We can solve that easy in the server project with a wrapper around the service provider instance, which would also provide a meaningful error message if someone tried to access...
I'm planning to write a scoped subscription execution strategy in the MicrosoftDI project after #3004 is merged, and remove the code that creates the scope from the server project.
That will be a breaking change of course. I don't have a good answer for how to do everything without a breaking change here. However, already it will be that...
No. The subscription lives on its own until disposed, and the original execution context's cancellation token is discarded. It is the responsibility of the server project to disconnect the subscription...
Agree. In general, current version should support current-1 spec at most. People can use v4 if they need old spec support.
In general, I can tell you that sharing GraphQL.NET graph type instances between different schema instances can lead to BIG problems, with the exception of scalar graph types. In fact,...