You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
. Add a line of LU data with error to the LU trigger phrase
. Notice that an error icon showing besides the "Start Bot" button
. Click the button to get the detail LU error notifications
. Click each error notification
. Composer jump to the Lu All-up view
Expect:
Composer shows the LU data with error I added.
Result:
the error data didn't show up in the view.
Version
Browser
Chrome
Safari
Firefox
Edge
OS
macOS
Windows
Ubuntu
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
Screenshots
. error data added
. error indicator
. error notifications
. when click the error notification item, composer jump to all-up view, and all data are correct there.
Additional context
The text was updated successfully, but these errors were encountered:
We've seen some back and force on the notification page behavior, let's meet to clarity the design and solve any potential design issues. @liweitian@lei9444@zhixzhan
I committed a fix, now error can navigate to all up view editor.
ps:
I remember previous a logic is if error happen on a dialog used intent, click will navigate to form editor. but now mostly will not, almost all error navigate to all up view.
After some debug, I found the reason is luParser can't parse every error intent, meanwhile our find error intent in dialogPath rely on parse results. That caused failed to calculate dialogPath, then failed to navigate to form editor.
Describe the bug
. Add a line of LU data with error to the LU trigger phrase
. Notice that an error icon showing besides the "Start Bot" button
. Click the button to get the detail LU error notifications
. Click each error notification
. Composer jump to the Lu All-up view
Expect:
Composer shows the LU data with error I added.
Result:
the error data didn't show up in the view.
Version
Browser
OS
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
. error data added
. error indicator
. error notifications
. when click the error notification item, composer jump to all-up view, and all data are correct there.
Additional context
The text was updated successfully, but these errors were encountered: