Do you need to unsubscribe from @Output EventEmitter

Question

On the Angular website they have an example of a Parent and Child component talking to each other using @Output() onVoted = new EventEmitter();.

Answer 1

If you see example on the Angular website and they don't unsubscribe then why do you think you should do it?

Angular takes care about it.

When it creates directive instance it subscribes to the outputs:

if (def.outputs.length) {
    for (let i = 0; i < def.outputs.length; i++) {
      const output = def.outputs[i];
      const subscription = instance[output.propName !].subscribe(
          eventHandlerClosure(view, def.parent !.nodeIndex, output.eventName));
      view.disposables ![def.outputIndex + i] = subscription.unsubscribe.bind(subscription);

https://github.com/angular/angular/blob/235a235fab45b2c82f8758fc9c0779f62a5b6c04/packages/core/src/view/provider.ts#L138-L140

and when it destroyes component it also automatically unsubscribes from output subscriptions:

export function destroyView(view: ViewData) {
  ...
  if (view.disposables) {
    for (let i = 0; i < view.disposables.length; i++) {
      view.disposables[i]();

So every time you destroy your directive angular will dispose all subscription for you.

But if you subscribe to EventEmitter manually in code then you have to unsubscribe yourself.

Answer 2

i think you don't have to do unsubscribe. Since You are not using child to parent component iteration for fetching data from API there is no need to unsubscribe.