Arincon
commented
6 years ago What Translation Middleware is doing is basically this:
context.onSendActivities(async (newContext, activities, newNext) => {
await Promise.all(activities.map(async (activity) => {
if (activity.type == ActivityTypes.Message) {
await this.translateMessageAsync(newContext, activity, targetLanguage, sourceLanguage);
}
}));
return newNext();
})
LarsLiden
msft-shahins
I was working on a demo bot from one of the samples on ConversationLearner-Samples , and I noticed some strange behaviour.
I added Translation Middleware (like this: v4 JS Translation Docs) and I have had one main problem. The problem appears when you train ConversationLearner to send to the user many messages in a row (without waiting for the user to reply). In this scenario, the first message is translated back to the user language, but the rest remain in english. I digged into the code to find the cause, and as I see, the problem is with the context. The translation middleware is adding a "listener" to the context, which executes every time a message is sent to the user. However, as you can see in CLRunner.ts:650, in all messages excepting the first, what CL SDK is doing is resuming the conversation, and getting a context from the ConversationReference object. My suspicion is that this context doesn't have, for some reason, any middleware attached.
Any clue on this?
Thank you in advance.