Hi folks! I have a question about Graphcool’s server-side implementation of subscriptions. From what I can see every subscription is managed by nested, project-specific and model-specific managers (e.g.

SubscriptionManagerForModel

). I see that each of those model-specific managers handles database events specific to that model (creation, deletion, update) and then re-executes subscription queries and sends the result back to the respective subscribers. That’s all pretty clear. How does Graphcool deal with subscriptions that include deeply nested relationships though? E.g. with a subscription like

subscription User {
  User {
    node {
      id
      name
      friends {
        interests {
          name
          tags {
            name
          }
        }
      }
    }
  }
}

Let’s say a tag or an interest is updated, how does Graphcool know that the above subscription is affected its query needs to be re-executed?

It doesn't, so it won't.

Oh 😄

The issue is tracked here: https://github.com/graphcool/framework/issues/146

Ah, perfect. Thank you!