Shane Krueger
Shane Krueger
I’m all for your PR where there’s two separate methods. I just would mark the old one obsolete, that’s all.
I think I’m fully in agreement with your plan. Just considering that this is the Field method, which could be used extensively, and/or by intermediary libraries, we should retain the...
Seems like a very simple validation rule would suffice here.
Perhaps in v5 we change ExecuteAsync to accept a configure delegate which configures an instance of ExecutionOptions. Or we just clone ExecutionOptions. But then we would need to clone its...
@sungam3r Any more thoughts on this? Seems like a make-work project.
@sungam3r Is this issue still applicable or has it been fixed with the schema validation code we've done recently?
I would not change this until we have a consensus, and if deemed worthy, change all similar places. There is no reason why this particular instance is more or less...
Related: - #3144
Federation 2 support is available for schema-first, code-first, and type-first schemas in GraphQL.NET 8.0 (still in beta at the time of writing). See: - https://github.com/graphql-dotnet/graphql-dotnet/pull/3921