This is more of a question rather than feature request. What is the meaning of the toggle between the API_LOCAL call name and the require entity name? It seems to change the entity text into "$QuoteItem". Is this the equivalent of the cosmetic LUIS toggle between entity/token view or something else?

Describe the bug
Some bot messages do not render in the trained dialogs UI, instead I get a stack trace with an error about a conversation id not being found.

To Reproduce
I see a lot of this in my current app, but not sure how to repro. I can send an export of the model if you provide an email.

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser: latest Chrome
• Version: 0.295.10

Describe the bug
I have added a new entity and need to modify a number of trained dialogs to recognize this entity. When I go into a trained dialog and click on the initial utterance, the train dialog pop up closes and if I click on the trained dialog again, I get an error window.

To Reproduce
Steps to reproduce the behavior:

1. Click on an existing multi turn trained dialog.
2. Click on the first utterance in the list. My assumption is that this would allow me to highlight where a new entity should be recognized.
3. The popup closes.
4. Click on the same multi turn trained dialog again.
5. The popup comes up but there's also an error window on the side with the text FETCH_HISTORY_ASYNC Failed
   TypeError
   Cannot read property 'split' of undefined.
6. Incidentally, the X or Close button do not work. I have to refresh the window to get it back to working order.

Expected behavior
I should be able to edit the entities recognized in the initial utterance.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser Chrome 67.0.3396.87 (Official Build) (64-bit)
• I'm using latest Samples Repo and pointing at version 0.269.2 of SDK.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Not sure if this is the right repo to report this issue. I am playing around with the Conversation Learner and creating new dialogs. When I train new dialogs and press Score Actions, I see the scores pop up. However, if I am reviewing a trained dialog, all of the scores show up as "Unknown". Seems unhelpful.

Much thanks!
-s

• Removed -

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL https://[email protected]/Microsoft/ConversationLearner-UI.git.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Describe the bug
Chrome console results in redux store error and blank UI.

index.tsx:31 process.env.NODE_ENV:  production
index.tsx:32 process.env.REACT_APP_AAD_APP_ID:  38f847d3-2b83-43ef-b833-50573ef2eda1
reduxStore.ts:22 Uncaught TypeError: Cannot read property 'settings' of undefined
    at f (reduxStore.ts:22)
    at Object.<anonymous> (index.tsx:40)
    at t (bootstrap 3668c91ae2ae7f330df8:19)
    at Object.<anonymous> (main.9ac9afce.js:74629)
    at t (bootstrap 3668c91ae2ae7f330df8:19)
    at bootstrap 3668c91ae2ae7f330df8:62
    at bootstrap 3668c91ae2ae7f330df8:62
f @ reduxStore.ts:22
(anonymous) @ index.tsx:40
t @ bootstrap 3668c91ae2ae7f330df8:19
(anonymous) @ main.9ac9afce.js:74629
t @ bootstrap 3668c91ae2ae7f330df8:19
(anonymous) @ bootstrap 3668c91ae2ae7f330df8:62
(anonymous) @ bootstrap 3668c91ae2ae7f330df8:62

To Reproduce
Install latest conversational learner SDK (0.274.6) and run the UI.

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser: Latest Chrome

Thanks!
-s