What's I'm missing from all the GraphQL examples seen out there is some kind of interaction with database.
I think I understand how to `resolve` a path into a object. Array of objects should be similar, right? And how do I then describe that object with GraphQL terms? Can `resolve` function of fields get this object passed in?
resolve() takes the current field AST node as one of its arguments. Mappings to more complicated backends will demonstrate use cases of where this is needed. From that field AST you can arbitrarily descend into a ton of information, e.g. the subfields of the current field.
Comments
What's I'm missing from all the GraphQL examples seen out there is some kind of interaction with database.
I think I understand how to `resolve` a path into a object. Array of objects should be similar, right? And how do I then describe that object with GraphQL terms? Can `resolve` function of fields get this object passed in?
Here's my toy attempt at implementing it https://gist.github.com/jawr/b4c585b69b8e83255513
resolve() takes the current field AST node as one of its arguments. Mappings to more complicated backends will demonstrate use cases of where this is needed. From that field AST you can arbitrarily descend into a ton of information, e.g. the subfields of the current field.
How does resolve deal with asynchronous calls? The name almost suggests that you might be able to return a promise?
Yes, you can return a Promise in resolve(). I believe it's mentioned in the first half of this talk: https://www.youtube.com/watch?v=gY48GW87Feo