Add asynchronous context manager for chat actions#77
Open
0zd0 wants to merge 1 commit intohydrogram:devfrom
Open
Add asynchronous context manager for chat actions#770zd0 wants to merge 1 commit intohydrogram:devfrom
0zd0 wants to merge 1 commit intohydrogram:devfrom
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.
Description
This PR introduces an asynchronous context manager (
action) to theMessagesmixin, allowing users to continuously broadcast a chat action (e.g., typing, uploading) without manually managing the loop.It creates a background task that resends the action every
delayseconds and automatically sendsenums.ChatAction.CANCELupon exiting the context block.Example usage:
Type of change
How Has This Been Tested?
Manually tested by running a bot and invoking the context manager with a 10-second sleep to verify the typing indicator remains active beyond the standard 5-second Telegram limit, and disappears exactly after the block exits.
enums.ChatAction.TYPINGwithasyncio.sleepenums.ChatAction.CANCELis properly dispatched on__aexit__Test Configuration
Checklist