fix: wrong id sent on "next" messages in pubsub

andyrichardson / subscriptionless

GraphQL subscriptions (and more) on serverless infrastructure

MIT License

93 stars 3 forks source link

Closed reconbot closed 3 years ago

reconbot commented 3 years ago

We were sending the hybrid connectionId|subscriptionId in the next messages instead of the subscriptionId.

Screenshot shows before and after