handler description & help about telebot

[tucnak]

Automatic /help handler is a sound idea very much indeed. That said, I find myself implementing /help differently every single time. Sometimes you want to have some sort of a FAQ, sometimes it's just a brief explanation of core mechanics, but usually you don't want it auto-generated.

I also believe that such auto-generated /help implementation must also account for Telegram's recent i18n support (see language_code within User) and at this point I can't really tell whether such feature is worth it.

adding more arguments to the Handle func would be a breaking change

Not necessarily. Handle is a set-up function and isn't supposed to be used heavily (only a handful of times, during the bot init process), we can rely on reflection to add "optional" arguments:

// Definition
func (b *Bot) Handle(prefix string, features ...interface{}) {}

// Uses
bot.Handle("/action", func (c Context) {})
bot.Handle("/action", "Description", func (c Context) {})

[irgendwr]

That said, I find myself implementing /help differently every single time. Sometimes you want to have some sort of a FAQ, sometimes it's just a brief explanation of core mechanics, but usually you don't want it auto-generated.

I think most of the implementations I've seen (ie. BotFather) would fit in a basic modular scheme:

<optional Title>
<optional Text>(possibly a summary of the bots purpose and general use cases)

<optional Category Title>
<optional Category Text>
    <optional Command> - <optional short command description>

I also believe that such auto-generated /help implementation must also account for Telegram's recent i18n support (see language_code within User) and at this point I can't really tell whether such feature is worth it.

Language support could also be done if each text was a map[string]string. (although even Telegram themselves don't seem to use this feature afaik)

That said... You are probably right, it might not be worth the time to implement such a feature.

[tucnak]

Closing for the time being. We might bring it back for v2.1 or whatever.