Shane Krueger
Shane Krueger
Updating for v8
Ref: - #3760
If there are any issues with GraphQL.NET v7, I may be able to help diagnose the issue. The server implementation is completely rewritten as @sungam3r indicated, and fixes many issues...
I would comment that @MikeKenyon 's original workaround is essentially identical to Entity Framework's implementation of `ToListAsync` - see here: https://github.com/dotnet/efcore/blob/bdd9846218b002005321efed1cf5195cae12f1f2/src/EFCore/Extensions/EntityFrameworkQueryableExtensions.cs#L2298 So again, unless the execution strategy undergoes a rewrite...
Note that code-first has a similar problem. My personal solution is to utilize a custom `IdGraphType` implementation which coerces the value to the correct .NET type. This only works if...
Can be fixed with new feature: - #3857
@OpenSpacesAndPlaces You should be able to use `AnyScalarGraphType` in most cases. I wrote PR #3257 but it's almost identical to what currently exists in `AnyScalarGraphType`. There's also PR #3246 but...
Or just update AnyScalarGraphType slightly and call it a day. It's just missing the code to convert a default value to a literal when printing the schema. This code is...
Fixed by #3257
As `SystemTextJsonSerializer` is part of the GraphQL.NET client library, I'm transferring this issue to the applicable repo. This behavior is the function of `System.Text.Json`'s design and not part of GraphQL.NET....