fullcalendar/fullcalendar-angular

Certain ng-template names don't work

arshaw opened this issue · 4 comments

arshaw commented

resourceLabelContent and a few others.

Originally reported in by @oliverguenther in #204 (comment):

I can't seem to get the resourceLabelContent ng-template to work. I couldn't get figure out the routing from the ContentChild to the custom rendering pipeline though to properly debug it. Do you have any pointers on where to look?

I have a minimal repo example here:
https://stackblitz.com/edit/angular-ivy-wbmq1i?file=src%2Fapp%2Fapp.component.ts,src%2Fapp%2Fapp.component.html

arshaw commented

The bug has been fixed in my local dev environment and will be in the next release.

In the meantime, as a workaround for resourceLabelContent you can use cellContent instead (the wrong name that will for only beta.4)

  • 👍1
oliverguenther commented

Hi @arshaw, thanks for getting back so quickly. On my app and the minimal repro example, cellContent doesn't appear to work either? The ContentChild seems to be present with that name: https://github.com/fullcalendar/fullcalendar-angular/blob/v6.0.0-beta.4/lib/src/full-calendar.component.ts#L53

  • 👍1
hoangdinhcong commented

Hi @arshaw, thank you for your hard work. I'm very excited to upgrade to version 6.0.0 with this new feature.

But I have some errors when trying to implement the resourceLabelContent and resourceAreaHeaderContent when using it in inside a dynamic dialog in primeng. When I close the dialog it shows these errors:

ERROR DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at TransportContainerComponent.ngOnDestroy (https://github-msefaz.stackblitz.io/turbo_modules/@fullcalendar/angular@6.0.0/fesm2015/fullcalendar-angular.mjs:164:24)
    at executeOnDestroys (https://github-msefaz.stackblitz.io/turbo_modules/@angular/core@15.0.3/fesm2015/core.mjs:6454:32)
    at cleanUpView (https://github-msefaz.stackblitz.io/turbo_modules/@angular/core@15.0.3/fesm2015/core.mjs:6364:9)
    at destroyViewTree (https://github-msefaz.stackblitz.io/turbo_modules/@angular/core@15.0.3/fesm2015/core.mjs:6197:17)
    at destroyLView (https://github-msefaz.stackblitz.io/turbo_modules/@angular/core@15.0.3/fesm2015/core.mjs:6342:9)
    at ViewContainerRef.remove (https://github-msefaz.stackblitz.io/turbo_modules/@angular/core@15.0.3/fesm2015/core.mjs:22721:13)
    at ViewContainerRef.clear (https://github-msefaz.stackblitz.io/turbo_modules/@angular/core@15.0.3/fesm2015/core.mjs:22564:18)
    at NgIf._updateView (https://github-msefaz.stackblitz.io/turbo_modules/@angular/common@15.0.3/fesm2015/common.mjs:3528:37)
    at set ngIf [as ngIf] (https://github-msefaz.stackblitz.io/turbo_modules/@angular/common@15.0.3/fesm2015/common.mjs:3495:14)
    at setInputsForProperty (https://github-msefaz.stackblitz.io/turbo_modules/@angular/core@15.0.3/fesm2015/core.mjs:12467:35)

I've created a Example here. Please take a look. Thank you so much 💪

arshaw commented

@oliverguenther, the ng-template bug you originally posted is solved in v6.0.0

@hoangdinhcong, please see this ticket:
fullcalendar/fullcalendar#7058
↑
Could you please visit the link, give a 👍 to vote (?), press the 🔈Subscribe button to receive updates?

  • ❤️2