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

Suggestion for on-responded on prompts #3981

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

alexrecuenco
Copy link
Contributor

@alexrecuenco alexrecuenco commented Nov 16, 2021

Fixes #3947

Description

On issue #3947, relying on the responded flag todecide whether to show the prompt interferes with logic that could be happening either

a. Concurrently
b. On some middleware
c. As part of how we reached the prompt

I believe the intention is to not send a prompt if the validator has already sent a message. This is in fact not explained anywhere and it leads to confusion, and restricts the ability to write concise explanations to users along side a retry.

Specific Changes

  • The default behavior is kept, except if a message was sent before the validator (Those are not considered as part of the prompt logic). This still runs into concurrency issues. For that,
  • A static method in Prompt has been added, setRepromptStatus. This allows the user to choose explicitly if the prompt should re-prompt or not.

Testing

  • Added extra tests for the new functionality only for the text prompt, since all other prompts reuse that same logic.

@ghost
Copy link

ghost commented Nov 16, 2021

CLA assistant check
All CLA requirements met.

@alexrecuenco alexrecuenco force-pushed the suggestion-on-responded branch 6 times, most recently from 94d57ab to c6c6dd9 Compare November 30, 2021 07:59
On issue microsoft#3947, relying on the responded flag todecide whether to show the
 prompt interferes with logic that could be happening either

a. Concurrently
b. On some middleware
c. As part of how we reached the prompt

I believe the *intention* is to *not* send a prompt if the validator has
 already sent a message. This is in fact not explained anywhere and it leads to confusion, and restricts the ability to write concise explanations to users along side a retry.

  - The default behavior is kept, *except* if a message was sent *before*
    the validator (Those are not considered as part of the prompt logic).
    This still runs into concurrency issues. For that,
  - A static method in Prompt has been added, setRepromptStatus.
    This allows the user to choose explicitly if the prompt should re-prompt or not.

- Added extra tests for the new functionality *only* for the text prompt,
    since all other prompts reuse that same logic.
@gabog gabog removed the request for review from sgellock March 21, 2022 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[botbuilder-dialogs] Dialog does not prompt on continue dialog if any activity is sent on the turn
1 participant