-
Notifications
You must be signed in to change notification settings - Fork 478
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add middleware to address transitional location of tenantId field #1754
Conversation
…workaround issue with MSTeams not sending the TenantId in Acivity.Conversation.TenantId. Replaced ArgumentNullException thrown by NullReferenceException (this is more apriopiate for the type of validatation that is being done). Fixed types and stylecop violations on BotFrameworkAdapter. Added unit tests for MSTeams workaround.
|
@benbrown, I updated the middleware to also check for ChannelId = MSTeams and also added some unit tests for it.
|
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.
looks right to me
|
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.
🕐
Added (c) notice to new test file.
|
This is the C# version of this Javascript PR
Description
This change handles the in-transition location of the tenant ID field for MS Teams.
Specific Changes
Load a middleware in the constructor for BotFrameworkAdapter that will look for channelData.tenant.id and copy the value to conversation.tenantId for use in createConversation.
Testing
adapter.createConversation
to create a DM with a user.