Fork me on GitHub
#graphql
<
2017-07-10
>
hlship18:07:04

hmaurer: I have something more ambitious going on in my branch, that makes it easier to arbitrarily extend or swap implementations of interceptors in the GraphQL routes. https://github.com/walmartlabs/lacinia-pedestal/tree/20170616-subscriptions

hmaurer16:07:27

very simple addition

hagmonk23:07:18

I've got a question about schema modeling, having just started using lacinia

hagmonk23:07:20

let's say I've got two queries at the root, "person" and "history"

hagmonk23:07:38

it's valid to nest "history" under "person" … in the resolver for "history" I'll detect the case where it's passed a resolver value from the "person" resolver, and I'll fetch that person's history

hagmonk23:07:30

it's also valid to ask for "history" at the root level, since you might get history results for things other than a person

hagmonk23:07:11

I'm not sure how to handle the declaration of "history" under the "person" object. Right now it has to be a complete copy of the "history" query at the root level

hagmonk23:07:40

what does one do in this case to keep things DRY?