{"componentChunkName":"component---src-templates-blog-post-js","path":"/blog/passing-callback-function-to-grandchild-in-angular/","result":{"data":{"markdownRemark":{"fields":{"published":"2020-10-17T10:00:02-07:00","lastModified":"2020-12-13T17:51:09-07:00"},"frontmatter":{"date":"2020-10-17T17:00:00.000Z","title":"How to pass a callback function to a grandchild component in Angular","description":"Calling a function from the child to the parent to the grandparent","tags":["angular","javascript","tutorial"],"featuredImage":null},"timeToRead":4,"html":"

Recently, I was refactoring some Angular components and I stumbled upon an issue of passing a callback function from a grandparent to the child component. Up to that point in time, I have only passed callback functions from the parent to the child by using the @Output() decorator and the EventEmitter class.

\n

Premise

\n

The idea here is that I wanted to create a generic base component and a more specific component that has the layout and functionality of the base component.

\n

For example, I have this alert component which has a dismiss button. I will create a generic alert component (base-alert.component.ts) that has the option to override the default onClick function of the close button.

\n

Next, I'll create a more specific alert component (cta-alert.component.ts) based off of that generic alert component that has a different dismiss button text than the generic alert component and allows the user to optionally override the default onClick function of the dismiss button.

\n

Meaning that, if I didn't pass a callback function to the cta-alert.component.ts component, it will default to the default onClick function that was defined in base-alert.component.ts.

\n

Here's how the relation between the components look like in this example:

\n\n

The problem

\n

So, yeah the idea is pretty simple. Use a the custom callback function if it was provided, otherwise use the default onClick function.

\n
<app-base-alert\n    (dismissButtonCallback)=\"dismissButtonCallback.emit()\"\n></app-base-alert>
\n

One of the first things that came to mind was to try and conditionally include the dismissButtonCallback directive in the cta-alert.component.ts component only if a callback function was passed in app.component.ts.

\n

From the grandparent to the parent component, I could see whether a callback function was passed by looking at the length of observers in the EventEmitter object. So if this.dismissButtonCallback.observers.length > 0, a callback function was passed.

\n

The problem came when I tried to do the same check in the child component. It always returned the length of 1 for the observers.length.

\n

This was due to the fact that, if the directive dismissButtonCallback is included, the @Output() decorator will always be initialized with an EventEmitter instance. This is regardless of what value I passed into that directive. I tried passing null and undefined and it still registered as an EventEmitter instance with and observers.length of 1.

\n
ERROR Error: @Output primaryButtonCallback not initialized in 'CtaAlertComponent'.\n    at listenerInternal (core.js:15201)\n    at Module.ɵɵlistener (core.js:15053)\n    ...\n    at ApplicationRef.bootstrap (core.js:28368)
\n

So, then I decided to conditionally initialize the @Output() decorator with an EventEmitter only if a callback function was passed from the grandparent component. But that didn't work as I was continuously getting the following error.

\n
export class CtaAlertComponent implements OnInit {\n  @Output() dismissButtonCallback?: EventEmitter<any>;\n\n  constructor() {\n    if (dismissButtonCallback) {\n      this.dismissButtonCallback = new EventEmitter();\n    }\n  }\n\n  ngOnInit(): void {\n    if (dismissButtonCallback) {\n      this.dismissButtonCallback = new EventEmitter();\n    }\n  }\n}
\n

I even tried to initialize the @Output() decorator in the constructor and the OnInit lifecyle hook but it seems to only like it when the EventEmitter is initialized when the @Output() decorator is defined.

\n

My solution

\n

In the end, I managed to get it working by passing the callback function from the grandparent to the parent component with an @Input decorator and I also created an overrideDismissButton property in the child component to help identify if the grandparent had passed a callback function or not.

\n

So, for the example below, if I clicked on the 'I Understand' button of the second alert, the message 'firing from app component' will appear in the console opposed to 'firing from base alert component' which is default onClick action of from the base-alert.component.ts component

\n
// app.component.ts\nimport { Component } from '@angular/core';\n\n@Component({\n  selector: 'app-root',\n  template: `\n    <app-base-alert></app-base-alert>\n    <app-cta-alert [dismissButtonCallback]=\"customCallback\"></app-cta-alert>\n  `,\n})\nexport class AppComponent {\n  customCallback(): void {\n    console.log('firing from app component');\n  }\n}
\n
// cta-alert.component.ts\nimport { Component, OnInit, Input } from '@angular/core';\n\n@Component({\n  selector: 'app-cta-alert',\n  template: `\n    <app-base-alert\n      [dismissButtonText]=\"'I Understand'\"\n      (dismissButtonCallback)=\"dismissButtonCallback()\"\n      [overrideDismissButton]=\"isCallbackPassed\"\n    >\n    </app-base-alert>\n  `,\n})\nexport class CtaAlertComponent implements OnInit {\n  @Input() dismissButtonCallback?: any;\n\n  isCallbackPassed: boolean;\n\n  ngOnInit(): void {\n    if (this.dismissButtonCallback) {\n      this.isCallbackPassed = true;\n    } else {\n      this.isCallbackPassed = false;\n    }\n  }\n}
\n
// base-alert.component.ts\nimport { Component, EventEmitter, Input, Output } from '@angular/core';\n\n@Component({\n  selector: 'app-base-alert',\n  template: `\n    <div>\n      <p>A simple alert component</p>\n      <button\n        type=\"button\"\n        (click)=\"\n          overrideDismissButton\n            ? dismissButtonCallback.emit()\n            : onDismissButtonClick()\n        \"\n      >\n        {{ dismissButtonText }}\n      </button>\n    </div>\n  `,\n  styles: [\n    `\n      div {\n        font-family: Arial, Helvetica, sans-serif;\n        display: flex;\n        justify-content: space-between;\n        padding: 1rem;\n        margin-bottom: 1rem;\n        background-color: skyblue;\n\n        p {\n          display: inline-block;\n        }\n      }\n    `,\n  ],\n})\nexport class BaseAlertComponent {\n  @Input() dismissButtonText?: string = 'Close';\n\n  @Input() overrideDismissButton?: boolean = false;\n\n  @Output() dismissButtonCallback?: EventEmitter<any> = new EventEmitter();\n\n  onDismissButtonClick(): void {\n    console.log('firing from base alert component');\n  }\n}
","fileAbsolutePath":"/opt/build/repo/data/blog/passing-callback-function-to-grandchild-in-angular.md"}},"pageContext":{"id":"b60b2063-608e-526d-a133-404f5600f169","previous":{"fields":{"slug":"/my-frustration-with-microsoft-services/"},"frontmatter":{"title":"My frustration with Microsoft services"}},"next":{"fields":{"slug":"/computer-science-education-week-2020/"},"frontmatter":{"title":"Behind the scenes of my CSEdWeek 2020 video series"}}}},"staticQueryHashes":["2493616844","3731164888"]}