Introduce <ChannelProvider /> to hoist channel connection about use-pusher HOT 6 OPEN

Thanks @jfulse, that’s definitely not intended! All subscriptions should continue to receive new events.

I think this could be solved by introducing a new ChannelProvider - it does the subscription there, passes it down via context and then the useChannel hook consumes the single connection. That would probably solve some other issues here too!

for now, I suggest hoisting your useChannel into a context and providing it high in your app, then using a custom hook to consume this. That way the connection stays live no matter which components get unmourned.

I’ll write an RFC soon.

from use-pusher.

Thanks for your response, sounds great!

from use-pusher.

just ran into the same issue, this would be greatly appreciated! Thanks for the great lib ;)

from use-pusher.

@jan-wilhelm Indeed, it does but what i would suggest @mayteio is that instead of just unsubscribing the channel (checking first if there are any more active subscribers) because this issue was related to having N subscribed and one of them would un-mount and leaves the channel (well this could be good just to help on those cases)

from use-pusher.

Same problem for me. Is there a known workaround to prevent unsubscribing if one of many components unmounts?

from use-pusher.

I just ran into this too. Looking forward to a fix.

from use-pusher.