-1

As per most of the blogs we don't need to explicitly unsubscribe the subjects once we call complete. I tried to subscribe the subject after calling complete on it. The complete call back was still executed.

let s = new Subject();
s.complete();

s.subscribe(
  () => {
    console.log("next");
  },
  () => {},
  () => {
    console.log("complete");
  }
);

Output: complete

Why subscribing to subject is allowed after it is completed?

deerawan
  • 8,002
  • 5
  • 42
  • 51
Shubham
  • 95
  • 13
  • 2
    Why are you surprised by this? What are you expecting to happen? – Kurt Hamilton Feb 19 '20 at 06:57
  • It's because of what `subscribe` is. You get a `next` callback, an `error` callback and finally the third: the `complete` callback. You are catching it hence you see the `"complete"` logged. – Jacopo Sciampi Feb 19 '20 at 07:34

1 Answers1

1

What happens in this case is that first, a 'complete' notification is dispatched, and immediately afterwards, the subscription is unsubbed. So it still holds that you don't have to unsub manually.

If you are wondering what's the use of subscribing in the first place, you can think of an example where we apply isEmpty operator to the subject, and do something depending on the value nexted by this operator.

Ivan
  • 1,317
  • 13
  • 23