Sergiy 🇺🇦

No activity for a long time, considering the issue was fixed If you have any other problem, please create a separate issue Thanks, Wundergraph Team

Hi @argoyle will it be possible for you to share subgraphs involved in your query and query itself? e.g. try to cut subgraphs and query to the smalles reproducible amount

Hi @argoyle sorry for the big delay could you try out a version from this [PR](https://github.com/wundergraph/graphql-go-tools/pull/818) I believe it should fix your problems with a typenames Thanks, Wundergraph Team

Hi @alexus37 Not sure, how it is blocking you, as other router implementations are doing the same It is not a bug, currently, it is designed like that It is...

@alexus37 We didn't know the details of your current/feature schema You have tested an example of multiple root fields, which may result in separate requests, but they anyway will be...

Hi @phob0s-pl Thanks for the report! This is an issue with early reporting that graphql document an invalid Right now it has low-priority If you are blocked with this issue...

Hi @mattjohnsonpint Basically, in our case, we anyway will add a Query type with introspection service fields But right now our introspection generator skips such [fields](https://github.com/wundergraph/graphql-go-tools/blob/master/v2/pkg/introspection/generator.go#L105) They could be added...

Hi @StevenACoffman thanks for the try Latest gqlgen requires some changes in the resolver, as the generated code changed a bit also, you could remove this line here https://github.com/wundergraph/graphql-go-tools/blob/16602c669d4fcd4c66cf52586d5cbfd6324c2bc9/pkg/astvalidation/reference/main.go#L14 to...

Hi @PeteMac88 Could you check with the `0.90.0` version?

Thanks a lot Could you also check `0.88.0`? We already know the reasons why it changes in 0.90.1 But it is a bit of a surprise that it also spikes...