Update testbot to parity with DotNet #954
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Separate the bot logic from the index.js file - Update the package-lock.json
cleemullins
approved these changes
Jun 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #953
Description
We updated the testbot project to have parity with the Botbuilder-DotNet implementation in the PR#1946 that configured an endpoint for each bot in the testbot project. To do that, we separated the bot logic from index.js file and added a new post method with the route '/api/mybot' to handle the messages sent to the mybot.
Additionally, we updated the package-lock.json to get the latest version of the botbuilder libraries.
Specific Changes
Testing