[Improve] Make Telegram task topic handoffs explicit#499
Merged
Conversation
Contributor
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.
Summary
Behavior
Before, the source message received an eyes reaction and the task topic appeared silently. A topic creation failure also silently started the task in the source chat.
After, the source conversation names the new topic and offers Open topic and Follow Task actions. If topic creation fails, the started message says why the task remained in the current conversation and points to Threaded Mode or Manage Topics.
The first preview shows the forum-supergroup variant. Private bot topics receive the same handoff, but direct users to Telegram's topic list instead of showing an Open topic deep link.
Topic handoff
Inside the task topic
Topic creation fallback
Real example
Validation