Muthu Kumar

> How do you name a buffer or stream? Now I get what you mean - I did it this way because of this: https://github.com/telegraf/telegraf/blob/e39398acddbaa80900460bc5a54c9f89fe04af7c/src/core/types/typegram.ts#L15-L32 Fixed in 4ad64f9e5d1cd4d742e8408fb0b7b03639ec5997

How about supporting RegExp in `bot.command`? * It's not implicit magic * It only costs a `typeof` check in the existing case At least two users have also asked me...

> should `Composer.command` check the username before trying the regex Yes, that would be reasonable.

#1388 partially related in the sense that manually narrowing context type will now be easier, since there was no officially supported way of doing so in the past. A full...

@KnorpelSenf I have access to npm `@telegraf/` now :) I don't have access to the GitHub org to create repositories yet. But this is the strategy for telegraf now -...

@Viiprogrammer That's a very good point - at the moment I don't think there's any way to reconcile fmt and i18n. > may be needed in the future. Any solution...

Fixed in #1714

`bot.catch()` catches `TelegramError`, but you must always `await` all your promises for it to work. For example, `await ctx.reply(...)` or `await next()`. If you don't add await/return for all async...

This was released to stable as [v4.11.0](https://github.com/telegraf/telegraf/releases/tag/v4.11.0), feel free to update now :)

@wojpawlik > I suggest merge-squashing or rebasing before merging I have rebased, but prefer not to squash history. Rather than treat git as a changelog, I prefer to treat it...