-
Notifications
You must be signed in to change notification settings - Fork 493
Fixed Teams TenantId/ChannelData issue #2481
Conversation
- Made MockAdapter.CreateConversation mimic actual code better
Pull Request Test Coverage Report for Build 78268
💛 - Coveralls |
|
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1 |
|
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1 |
|
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1 |
cleemullins
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you make the JS Change? We need it in both spots:
https://github.com/microsoft/botbuilder-js/blob/b0793cea52b8307dd5737a98c924995bc1766ec4/libraries/botbuilder/src/botFrameworkAdapter.ts#L277
Once that's ready, we can merge both.
|
... and please check Python. To my reading this change is needed there as well: |
|
@cleemullins On it. Should be able to knock out both tomorrow. Edit: I've got a support ticket that might delay this. Will have it done by the end of the week, regardless. Edit 2: Support ticket has evolved into another. Will push to next week. |
|
@cleemullins This one good to merge? |
Fixes: #2480
Issue
BotframeworkAdapter.CreateConversationstrips out the ChannelData of the message here. As you can see per linked issue, this can cause problems when usingCreateConversationwith Teams since Teams requiresTenantIdon theChannelData.I also fixed up an issue where
MockAdapter.CreateConversationwasn't mimicking our actual code, which would have caught this issue earlier.Changes
BotFrameworkAdapter.cs
MockAdapter
Testing
No new tests needed. Previous test erroneously covered this and that test has been fixed in the PR via the above change. Only 175 because a few live ones were skipped and a couple Azure ones don't seem to want to pass for me unless I run them separately (I think it has to do with Storage Emulator)
I also tested this in a few simple bots, including one that creates a Teams conversation using this change and it worked fine.
Help
Due to adding additional
ChannelDatatoCreateConversation, I'm not comfortable saying this PR isn't a breaking change. I'd be a little surprised if this were a breaking change, but it just seems like an odd thing to have not been included prior.ChannelDataisn't some weird breaking change