Improve schema delegation API for `graphql` handler about graphql-mesh HOT 4 CLOSED

What is the purpose of the nodes field? Why do you want it on root fields but not when linking schemas?

For long term ideas about query/result processing, see here: https://yaacovcr.github.io/apollo-stitcher/tutorial-Motivating%20Example.html

I think use of PreStitch pseudofragment is cool, want to integrate that into fork in long term, as well as provide method of only traversing result once with multiple transforms, will likely require making a single transform that can do multiple things...

from graphql-mesh.

It's actually coming from the automatically-created schema (for example, the output of postgraphile), or from a remote schema (for example, GitHub GraphQL schema). So I have no control over that.
The idea behind removing it is to allow simple inerface and usage for the consumer.
In this case, it uses Github_search behind the scenes, and it might returns multiple types, not only Github_User, under nodes. But from the consumer point-of-view, we would like to expose it directly as Github_User and not as Node, because we are able to make sure that's only those object will be returned by the root API.

It does seems like the stitcher idea might work in this case, it might be useful for the fork and mesh as well :)

Thanks @yaacovCR !

from graphql-mesh.

Implemented by @ardatan in: #142

from graphql-mesh.

Available in 0.0.17 🎉

from graphql-mesh.