get_chat_history: add min_id & max_id parameters #1366
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.
I'm switching lib from telethon because poor perfs, good news is that I retreive messages instantly now, was not the case with telethon.
But the way my code works I keep track of the last (most recent) message retreived from history - this is conveniently handled via
min_id
param to Telegram's API, which is not passed down to base request in pyrogram. (offset_id
does the work in reverse, probably acting similar tomax_id
, not sure if there is a difference)So here is my small contribution. I've also added
max_id
along the way but reflecting on what I just said maybe it would add confusion.This does the job for me, could help others. Could also be included in
get_messages
andsearch_messages
perhaps, for now I only useget_chat_history
.