Added support for group topics #132
Open
Conversation
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
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.
This PR adds support for topic-structured groups, officially known as forums. This was requested in Issue #131. Legacy supergroup behaviour is unchanged; new logic is only applied when telegram_send detects that it is being configured to work inside a forum. Topic-separation works by replying to a "forum_topic_created" message. An additional configuration field was added to keep a permanent reference to this message, called "reply_to_message_id". If "reply_to_message_id" is present in the configuration, the bot will always reply to that message, which will result in a message appearing inside a topic. Examples of reworked logic are shown below:
Legacy groups:
Forums:
Forums (alternated topic):
New configuration:
Old configuration:
