I fixed issue 39 in the channel component by using debounceTime(50) instead of a delay or setTimeout as it adds the benefit of minimizing re-rendering after each agendaItem is added if initialization happens in ngAfterViewInit() of the event-scheduler (demo) instead of ngOnInit(). In ResourceChannelMapData I changed the subject to use a BehaviorSubject instead of ReplaySubject so that if there isn't any initial agendaItems the channels still initialize to one big drop-zone. In agend-item component I stopPropagation on delete click so that it doesn't open the editor for the item just deleted, which was the click passing to the agend-item.
I fixed issue 39 in the channel component by using debounceTime(50) instead of a delay or setTimeout as it adds the benefit of minimizing re-rendering after each agendaItem is added if initialization happens in ngAfterViewInit() of the event-scheduler (demo) instead of ngOnInit(). In ResourceChannelMapData I changed the subject to use a BehaviorSubject instead of ReplaySubject so that if there isn't any initial agendaItems the channels still initialize to one big drop-zone. In agend-item component I stopPropagation on delete click so that it doesn't open the editor for the item just deleted, which was the click passing to the agend-item.