Graphql-subscriptions: allow resolver fn to be async

I am not sure if this was the correct place but was wondering if we could get some eyes on the issues and PR below and get any feedback. We have a use case where we are returning an AsyncIterator asynchronously in the subscription but is not allowed.

2 Likes

@bpallares we’ll take a look!

2 Likes