Access to rootValue about graphql-weaver HOT 2 OPEN

Thanks for your feedback. You're correct, the rootValue is currently not propagated. It makes sense to propagate the rootValue to endpoints without namespace declaration, like in your example. Does your use case also include endpoints with namespaces? I think it would still be a good idea to set the rootValue in the GraphQLResolveContext, but what about source? Should it be set to the rootValue`? Should we just try to access a field on the rootValue with the same name as the namespace on the endpoint?

from graphql-weaver.

hmm... in my particular case only the "old" schema, which has no namespace declaration, would use a rootValue, the other weaved schemas with namespaces are from upstream services, so the rootValue is not really useful to them. But I can imagine that other people might try to weave local schemas that implement patterns such as the one DataLoader per request with namespaces. Using fields with the same name on the rootValue sounds good.

from graphql-weaver.