resolvers management about apollo HOT 5 CLOSED

Yes the above could already be done today and could be just shipped as utilities.

from apollo.

Composing resolve functions is a great idea! Sashko and I have been toying with the idea a little bit, but I haven't implemented anything for it.

Composing resolvers in the way you propose is actually already possible right now, so I think it would just be a matter of making an 'official' recommendation of how people should do it.

Just one question: I don't really see any namespacing in your examples. Maybe we could add that with a simple function where you can give both the field and the resolve function a prefix or something?

Ideally, we'd like to be able to compose both type definitions and resolve functions, such that every type would be 'portable' and could be plugged into any schema.

from apollo.

Could I see a sketch of this?

Ideally, we'd like to be able to compose both type definitions and resolve functions, such that every type would be 'portable' and could be plugged into any schema.

Having trouble visualizing this in my head!

from apollo.

Should we move this to https://github.com/apollostack/graphql-tools? Seems more relevant to the server component!

from apollo.

yes def!

from apollo.