You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.
As mentioned in the original post, the call is made by StrawberryShake as this is how it builds its introspected schema. I don’t know why it does it that way, other introspection queries work for us.
We use the library in various Server and Desktop applications and it would be nice if we could do the introspection to acquire the schema. The workaround for now has been to download the schema from studio and put this alongside the project (so it doesn’t automatically download it from the server).
The StrawberryShake introspection has worked with other routers, so I was surprised to see the query returning null for __Type!
Component(s)
router
Component version
0.110.1, 0.118.0
wgc version
0.62.0
controlplane version
0.104.0
router version
0.110.1, 0.118.0
What happened?
Description
When I try to make an IntrospectionQuery using StrawberryShake (.NET client), the .NET code cannot parse the result. The query looks like:
The result comes back from the router as:
Steps to Reproduce
I have reproduced this using multiple versions of the Router. I believe it is completely agnostic of the subgraphs within the system.
This should be reproducible on the code found in the demo.
Expected Result
Based on an alternative Federated router implementation, I would expect the result to be:
Environment information
No response
Router configuration
No response
Router execution config
No response
Log output
No response
Additional context
Apollo Router produced the expected result above, as did the graphql-yoga server. I assume it is a part of the intended GraphQL spec?
The text was updated successfully, but these errors were encountered: