Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggest capability to centralise resolve functions out of the type definitions #93

Closed
serle opened this issue Jul 29, 2015 · 2 comments
Closed

Comments

@serle
Copy link

serle commented Jul 29, 2015

I think it would be more manageable to separate the resolve declaration in the type schema from the resolve implementation code. This could enable the back-end resolve implementations to be produced by independent server-side teams potentially in other languages all together.

@leebyron
Copy link
Contributor

I'm sorry I don't quite understand what you're asking for here. Could you please write some example code that you wish you could write that you can't now?

@leebyron
Copy link
Contributor

leebyron commented Apr 7, 2016

Closing this aging issue.

For posterity: You can always construct types in graphql-js in any way that is legal JS, that can include defining resolver functions in one file and referencing them in another if that feels better for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants