pattern for getting initial subscription payload about graphql-subscriptions HOT 3 CLOSED

@dnalborczyk
The actual pattern for this use case is to use Query to fetch the initial state, and then use subscription to get real-time updates about data changes (usually the changes are driven from a mutation).

If your use case insist on publishing data when client connects, you can use onOperation callback of the subscriptions-transport-ws and publish data there, but note that your PubSub is shared between all clients, so you probably need to create your own implementation for AsyncIterator that wraps an existing Iterator (the shared one from your PubSub) and adds a custom payload publication for a specific user.

from graphql-subscriptions.

I was in the same situation and this blog post was great.

https://ralexanderson.com/blog/subscription-only-graphql-data

from graphql-subscriptions.

just noticed I didn't leave a message back in June :/

thank you so much @dotansimha !!!

from graphql-subscriptions.