Skip to content
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

[Linting & Validation] LU error is not removed after selecting 'none' recognizer type #1744

Closed
a-b-r-o-w-n opened this issue Dec 9, 2019 · 1 comment
Assignees
Labels
R8 Release 8 - March 16th, 2020

Comments

@a-b-r-o-w-n
Copy link
Contributor

a-b-r-o-w-n commented Dec 9, 2019

Current workaround

If you are no longer using an LU file and are seeing this, you can either delete the file or correct the syntax error in the file and then refresh the page.

Steps:

  1. Create a dialog and select LUIS recognizer type
  2. add invalid LU -- see an error inline and in the notifications page
  3. Select None in the recognizer type dropdown
  4. Notice the LU error still shows in the notifications page.

Side effect of this is that a user is unable to start a bot because there is an error even though LU is not being used.

@a-b-r-o-w-n a-b-r-o-w-n added the Needs-triage A new issue that require triage label Dec 9, 2019
@cwhitten cwhitten added R8 Release 8 - March 16th, 2020 and removed Needs-triage A new issue that require triage labels Dec 10, 2019
@cwhitten
Copy link
Member

Diagnostics/Indexer should not block the runtime if there is an error in the .lu, but the .lu is not being used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R8 Release 8 - March 16th, 2020
Projects
None yet
Development

No branches or pull requests

4 participants