Shane Krueger

I’m not sure. It sounded like the identical issue to mine so I posted the link. I had 2 viable workarounds which both worked for me, one being to ensure...

Most likely you need to call `FieldAsync` rather than `Field` for some of your field definitions. See: https://graphql-dotnet.github.io/docs/migrations/migration5#32-valuetask-execution-pipeline-support-changes

I'd further guess that the field type in this case is an interface or union, and what happened is that IsTypeOf returned false for the `Task` returned value, causing the...

Right I see. `AsyncNodeGraphType` (which is in the relay project) inherits from `NodeGraphType`, and when you call `Id` it calls `Field` instead of `FieldAsync`. The relay project's `AsyncNodeGraphType` needs to...

See faulty code here: (when used by the derived `AsyncNodeGraphType` -- the code is fine as `NodeGraphType`) https://github.com/graphql-dotnet/relay/blob/5ad6b1c6367a2cfd83894a1f2f1f761a62c36b4d/src/GraphQL.Relay/Types/NodeGraphType.cs#L91..L98 There's nobody that actively works on this project, but if you'd like...

@sungam3r I suggest moving this suggestion to the relay repo.

.NET 6 has not been released yet. Is there so much difference that we cannot use the .NET 5 server for the SPA? It should be fine if the SPA...

It looks like .NET 6 is scheduled for release in November. Not that far away.

Certainly don’t want to manage the spa setup but if the .NET csproj targets .NET 5 rather than .NET 6 most likely everything else (such as create-react-app, which does the...

Sounds fine. I can't push an updated package to nuget anyway. See #110