Few Questions

[01]

Few Questions

[wictorwilen]

Hi @01 and thanks for the feedback!

1. The reason it is implemented this way, more of a botbuilder middleware than the current beta of botbuilder-teams, is due to the way the botbuilder-teams implemented their way of the activity processor (which in my opinion feels and looks like a clunky way of doing the event handling - I would have preferred a more botbuilder middleware approach) and how you need to shove all code into the bot implementation deeply nested in the activity processor. For instance if you're building a message extension, and not a bot, (which I think is a very common case) you're adding a lot of overhead using the activity processor from botbuilder-teams.

2. Secondly, this was designed for the Microsoft Teams Yeoman Generator and more specificallly to its hosting component express-msteams-host - to make it easy to build message extensions and to be able to separate that logic out from the bot implementation and have a great way to support multiple message extensions (and easily add/remove those)

3. Almost same as above. Most invoke commands sends the commandId but unfortunately not composeExtension/onCardButtonClicked and composeExtension/selectItem. So when in the case that you have multiple message extensions you need to handle the case that this will be invoked for all your message extensions (using the same bot endpoint). And yes, this is only an issue where you have multiple message extensions for the same bot.

4. The onCardButtonClick reacts to the composeExtension/onCardButtonClicked which happens when you click on an Action.Submit action in a card in a conversation.

Great comments and questions, looking forward to more feedback!