-
Notifications
You must be signed in to change notification settings - Fork 479
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
[Teams] Hackathon feedback #2740
Conversation
…sionAction and not MessagingExtensionQuery. Change bad preview edit/send and bad file consent to return BadRequest.
…d if there is don’t overwrite it. OnTeamsSigninVerifyStateAsync returns void (create InvokeResponse internally)
Pull Request Test Coverage Report for Build 83559
💛 - Coveralls |
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3 |
… to TaskModuleResponse.
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3 |
…xception for OnTeamsFileConsentAsync and OnTeamsMessagingExtensionSubmitActionDispatchAsync
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3 |
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3 |
|
||
public InvokeResponse CreateInvokeResponse() | ||
{ | ||
return new InvokeResponse { Status = (int)StatusCode }; |
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.
so we could add message text in here... not blocking this PR as this is all internal
Fixes:
#2737
and
#2718
• Remove the tenant filtering middleware from the product, and add to samples
-Removed TeamsTenantFilteringMiddleware from the product and added it to Roster bot as an example.
• Bot message preview edit/send return value should be bad request if malformed
-now returning BadRequest
• File consent should be bad request if malformed
-now returning BadRequest
• OnTeamsMessagingExtensionFetchTaskAsync should take a MessagingExtensionAction and not MessagingExtensionQuery
-Changed parameter type
• In TeamACtivityHandler we should check whether there is an InvokeResponse activity on the turnstate and if there is don’t overwrite it.
- added check of TurnState for existing InvokeResponse
• OnSigninVerifyStateAsync should be void (create invoke response internally, if not present in turnstate)
- Changed return type to void, added test
• Change TeamsActivityHandler's task/fetch and task/submit return types to TaskModuleResponse