Consider handling the errors thrown in setupFunction and make it promisable. about graphql-subscriptions HOT 5 CLOSED

Would you mind opening two specific issues? It looks like there are two different feature requests rolled into one here.

from graphql-subscriptions.

You're right. Done.

from graphql-subscriptions.

Please, consider this issue.

from graphql-subscriptions.

@ ezsper This looks like a helpful improvement. A PR would be very welcome!

from graphql-subscriptions.

@ezsper We recently released a new version of the package, and now SubscriptionsManager and setupFunctions are deprecated. Instead, you can implement your own AsyncIterator as the event stream.
You can implement the filter using withFilter in your subscribe resolver that wraps existing AsyncIterator with a custom filter function (you can also return Promise there), and you can add the payload transformation using resolve (which also accepts Promise as return value).

{
    issuedUserNotification: {
        resolve: (payload) => { return payload; } // transformation,
        subscribe: withFilter(() => pubsub.asyncIterator('myEvent'), () => true) // filter
   },
}

from graphql-subscriptions.