Right now the media groups are simply different Message updates grouped together by a unique media_group_id. This implementation lacks a major thing that it gives no context about how many updates are left to receive.
According to PTB the best way is to start a timer, and listen the messages only received in the time frame. Which is pure garbage. (I'm sorry to say this tho). The other way is to make the user send a "finished" interaction, which is also kind of dumb in many situations. For example, let's say my bot is waiting for 3 photo messages. User sends 5, my code might invoke photo handlers redundantly, giving users negative experience.
So, I'd say if we can have a media_group_item_count or something like that, to actually determine the total number of items in the media group, that'd be amazing. With this we can actually expect this many number of items.
Thanks!
Right now the media groups are simply different
Messageupdates grouped together by a uniquemedia_group_id. This implementation lacks a major thing that it gives no context about how many updates are left to receive.According to PTB the best way is to start a timer, and listen the messages only received in the time frame. Which is pure garbage. (I'm sorry to say this tho). The other way is to make the user send a "finished" interaction, which is also kind of dumb in many situations. For example, let's say my bot is waiting for 3 photo messages. User sends 5, my code might invoke photo handlers redundantly, giving users negative experience.
So, I'd say if we can have a
media_group_item_countor something like that, to actually determine the total number of items in the media group, that'd be amazing. With this we can actually expect this many number of items.Thanks!