Idea: Add helpers to intersect a query on the server to get relevant data

type CommentCreateSubscriptionInput {
  clientMutationId: ID!
  storyId: ID!
}

subscription A($input_1: CommentCreateSubscriptionInput) {
  123Comment: commentCreateSubscription(input: $input_1) {
    commentEdge {
      cursor
      node
    }
  }
}
// When relay prints the query they rename the variables to input_1 input_2 etc. So we can't know for sure what pairs if we don't parse the query.
send(query, variables = { input_1: { clientMutationId: '1', storyId: '123' }});


// server
getVariablesForQuery(query, schema, {
  commentCreateSubscription: (arguments) => { // this will be called for the 123Comment field
    pubsub.subscribe(`comment_create_${arguments.input.storyId}`, sendPayloadToClient);
  }
});

What if we can intersect this query without executing it and get all variables paired with a subscription. Then we can move the subscription creation from the resolve handlers on the server and still get rid of the separate topic that I send along the query in the todo app (create the topic server side instead of letting the client decide).

Does this make sense? I don’t know…

[nodkz]

Yep, I missed.

Anyway may be you didn’t see talks about subscriptions, and can catch some good ideas: Standalone talk of Laney Kuenzel about subcriptions https://www.youtube.com/watch?v=mmke4w4gc6c Talk with Lee on React Europe https://www.youtube.com/watch?v=ViXL0YQnioU

And of course, let ask @leebyron and @laneyk give some advice how to implement creation of subscriptions.

[edvinerikson]

👍