[BUG] `IoEventContextToken` is not exported about ng-dynamic-component HOT 3 CLOSED

@daweedm the .bind() workaround for sure works but it's inefficient as this call will be performed every time your component's view is change-detected, so IoEventContextToken is meant to optimally do this for you.
As a more performant workaround you can use arrow function for an event handler method on your component so it's already bound by default.

But it's a good catch, the IoEventContextToken must be part of the public API.
I will create a fix for this soon.

from ng-dynamic-component.

@gund I found a workaround by using .bind(this) directly in the template :

<ng-template
    [ngComponentOutlet]="PointingScreenItemComponent"
    [ndcDynamicInputs]="{item: item}"
    [ndcDynamicOutputs]="{selected: onItemSelected.bind(this)}"
    *ngFor="let item of items"></ng-template>

Since function context binding works in the template, isn't IoEventContextToken redundant ?

from ng-dynamic-component.

🎉 This issue has been resolved in version 10.6.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from ng-dynamic-component.