This repository has been archived by the owner on Jun 30, 2022. It is now read-only.
Various docs issues #2310
Merged
Various docs issues #2310
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
…garding configuration and incoming/outgoing events
lzc850612
approved these changes
Sep 5, 2019
darrenj
approved these changes
Sep 10, 2019
ppaltmann
reviewed
Sep 10, 2019
| @@ -25,6 +25,8 @@ When deployment is complete, you can run your Virtual Assistant debugging throug | |||
|
|
|||
| 4. Populate the fields in the **Open a Bot** modal with your bot's configuration settings. Provide the endpoint of your running bot, e.g: `http://localhost:3978/api/messages`. Provide the AppId and Secret values. Find these in your `appsettings.json` file, under the `microsoftAppId` and `microsoftAppPassword` configuration settings. | |||
|
|
|||
| > **Note**: If you password has any JSON reserved characters (backslash, quote, etc.), they must be properly escaped to connect to your bot. | |||
There was a problem hiding this comment.
Hi @ryanlengel,
it is the other way around. If you enter the password with the slash inside of your deployment scripts (VA tutorial) it will be AUTOMATICALLY escaped. You don't need to do it by yourself. The problem is that this is happening without notice and when you follow the tutorial then you don't know that this operation happened and copy the wrong password out of the appsettings.json.
This means keep on eye on the appsettings.json if your password had escaped characters which you need to remove before entering it in the Bot Emulator.
There was a problem hiding this comment.
Got it - will fix.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Purpose
What is the context of this pull request? Why is it being done?
Close #2309 by adding additional details to the experimental skills page regarding configuration and integrating event activities
Close #2294 by updating each skill's README with an aka.ms link to the appropriate doc resource
Close #2288 by updating the To Do Skill's documentation and manifest file with an additional
User.ReadscopeClose #2274 by clarifying instructions in the VA Getting Started tutorial on getting LUIS credentials
Close #2332 adding a note to escape special characters
Changes
Are there any changes that need to be called out as significant or particularly difficult to grasp? (Include illustrative screenshots for context if applicable.)
n/a
Tests
Is this covered by existing tests or new ones? If no, why not?
n/a
Feature Plan
Are there any remaining steps or dependencies before this issue can be fully resolved? If so, describe and link to any relevant pull requests or issues.
n/a
Checklist
General