Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix for issue #151 on github where strings from LUIS models were not …
…handled properly.
- Loading branch information
Showing
1 changed file
with
2 additions
and
1 deletion.
There are no files selected for viewing
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
e81b9dd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this work? I tried this myself and found that although strings were passed to the field names correctly, commands such as 'quit' were no longer accepted for a field if a Luis Entity wasn't passed in
e81b9dd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you be more specific on what you mean by commands like 'quit' were no longer accepted? If you mean the step was skipped if there is a value, that can be controlled by passing in FormOption.PromptFieldsWithValues when you construct FormDialog.
e81b9dd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No.
For example, I have two string fields on my FormFlow. If only one of them is populated by a Luis entity, the other field was prompted as you'd expect. However, it didn't seem to accept 'quit' as a command to end the FormFlow if you entered it for that second field.
I will admit I did very limited testing and checking as I was doing several other things to the code as well.
Also, I'm having no issues with the latest V1.1 in this area neither, so I believe everything is working