Alex Recuenco (@alexrecuenco) were you able to hit this bug in actual usage?

From an initial investigation, it looks like this was code used as preparation for another set of features that are not currently in this SDK

Alex Recuenco (@alexrecuenco) were you able to hit this bug in actual usage?

From an initial investigation, it looks like this was code used as preparation for another set of features that are not currently in this SDK

Yes. I emit events, and then those events get captured by a parent component to do some resource refresh handling

My hotfix is to monkey-patch emit to be equal to emit event. With that monkey-patch, this works perfectly well.

The feature exists in the botbuilder-js, and here it is working perfectly well once you do that.

Yes. I emit events, and then those events get captured by a parent component to do some resource refresh handling

In particular, this is doing some life cycle generic component, that I am hoping to open source soon.

Any resource that is generated through a dialog with a user is encapsulated.

In particular, the main use is something akin to an authorization middleware within a bot. So you have an AuthorizedComponent that generates the sufficient context, and this component encapsulates token authorization.

The internal dialog then has in the turn state the reference to the required resource/authorization, without having to manually handle authorization in each dialog.

And for long running tasks, internal resources can extend that token by calling refresh(dialog_context), that in turns emits an event and is captured by the nearest matching AuthorizedComponent that refreshes the token/resource.

You approved it, but does it need anything else to he merged?

I see it is still not executing the tests, it says that it needs maintainer permissions.