Unsubscribe handling

[ShadowWolf308]

How do i prevent the onNext from being called for a subscription after receiving a complete messsage from the client?

I have tried removing the iterator from context.subscriptions but it still calls the onNext regardless.
The onComplete listener in useServer also does not get called after receiving a complete message from the client, i do receive this message on webSocket.onMessage however.

[enisdenjo]

The onNext callback is bound to the subscription async iterable. You can prevent it from being called by properly disposing/returning your subscription iterable which will in turn break that loop and stop invoking the onNext callback.

Also, the fact that the onComplete callback is not invoked prooves the point that your iterable is not being completed properly.

[ShadowWolf308]

And how do i properly dispose of that iterable?

i tried using delete context.subscriptions and that didn't work.

i have been looking for a while to see if i could find any documentation on disposing of subscriptions properly but couldn't find anything.

[enisdenjo]

The issue is not in graphql-ws at all, there's nothing you should/can do there. The issue is with your subscriptions in the graphql resolvers.

[ShadowWolf308]

I found why my unsubscribes aren't working, thanks for the support. it was indeed in the subscription of the resolver.