fix(gateway): enable text-intercept for multi-choice clarify fallback (#25587)#25778
Merged
Conversation
Contributor
🔎 Lint report:
|
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
3 participants
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.
Multi-choice clarify prompts on platforms that don't support inline buttons (Mattermost, generic webhook) need text-intercept fallback so the user can type their answer. The text-fallback path was missing the
mark_awaiting_text()call, so subsequent text messages weren't routed to the open clarify.Adds the missing call inside the text-fallback path of
base.send_clarifyplus a regression test.Closes #25567.
Salvage of #25587 by @zccyman.