Fixed retry prompting in NumberPrompt by adding await #302
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #281
Changes
Originally retry prompts were not sending to the user when an invalid value was sent to a
NumberPrompt(e.g. "Please enter a number" "hello" <-- invalid)This was happening simply because
NumberPromptwas missing an "await" for sending an activity if it passed the condition of needing to send a retry prompt.Uncommented tests that were previously ported that were breaking for retry promps and validation
Screen shots
Expected Behavior (plugging a
NumberPromptinto CoreBot real quickly)