handling subscriptions reactively about react-rxjs HOT 1 CLOSED

After having put a lot of thought into this, I think that the approach that we are promoting on the "Github Issues Viewer" should be one of the recommended ways of approaching this. There are nuances, of course, but overall I think that's the most straightforward CM compliant way to approach this.

In a nutshell our recommendation should consist in creating top-level subscriptions that listen to a stream that indicates whether that component is going to be used, and perform a switchMap so that if the component is not going to be used it returns EMPTY and if it's going to be used it returns the observable(s) that are going to be consumed inside the component.

There are other cases, of course, like when you have a subscription that can only start after a user-action (submit-form, etc), in that case a basic useSubscribe would suffice. That's why I'm planing to add a section that explains these different cases in detail. However, the point that we are making in the docs is pretty clear and CM compliant: those subscriptions should exist before React attempts to use his.

from react-rxjs.