telegram-click

Click inspired command-line interface creation toolkit for python-telegram-bot.

Try the latest version of the example.py out for yourself: @PythonTelegramClickBot

Features

• POSIX style argument parsing
  • Quoted arguments (/command "Hello World")
  • Named arguments (/command --text "Hello World")
  • Flags (/command --yes)
  • Optional arguments
  • Type conversion including support for custom types
  • Argument input validation
• Automatic help messages
  • Show help messages when a command was used with invalid arguments
  • List all available commands with a single method
• Permission handling
  • Set up permissions for each command separately
  • Limit command execution to private chats or group admins
  • Combine permissions using logical operators
  • Create custom permission handlers
• Error handling
  • Automatically send error messages if something goes wrong
  • Optionally send exception messages

telegram-click is used by

• InfiniteWisdom
• DeineMudda
• grocy-telegram-bot

and hopefully many others :)

How to use

Install this library as a dependency to use it in your project.

pip install telegram-click

Then annotate your command handler functions with the @command decorator of this library:

from telegram import Update
from telegram.ext import CallbackContext
from telegram_click.decorator import command
from telegram_click.argument import Argument

class MyBot:

    [...]

    @command(name='start', description='Start bot interaction')
    def _start_command_callback(self, update: Update, context: CallbackContext):
        # do something
        pass

    @command(name='age', 
             description='Set age',
             arguments=[
                 Argument(name='age',
                          description='The new age',
                          type=int,
                          validator=lambda x: x > 0,
                          example='25')
             ])
    def _age_command_callback(self, update: Update, context: CallbackContext, age: int):
        context.bot.send_message(update.effective_chat.id, "New age: {}".format(age))

Arguments

telegram-click automatically parses arguments based on shlex POSIX rules so in general space acts as an argument delimiter and quoted arguments are parsed as a single one (supporting both double (") and single (') quote characters).

Naming

Arguments can have multiple names to allow for abbreviated names. The first name you specify for an argument will be used for the callback parameter name (normalized to snake-case). Because of this it is advisable to specify the full argument name as the first one.

Types

Since all user input initially is of type str there needs to be a type conversion if the expected type is not a str. For basic types like bool, int, float and str converters are built in to this library. If you want to use other types you have to specify how to convert the str input to your type using the converter attribute of the Argument constructor:

from telegram_click.argument import Argument

Argument(name='age',
         description='The new age',
         type=MyType,
         converter=lambda x: MyType(x),
         validator=lambda x: x > 0,
         example='25')

Flags

Technically you can use the Argument class to specify a flag, but since many of its parameters are implicit for a flag the Flag class can be used instead:

from telegram_click.argument import Flag

Flag(name='flag',
     description='My boolean flag')

Permission handling

If a command should only be executable when a specific criteria is met you can specify those criteria using the permissions parameter:

from telegram import Update
from telegram.ext import CallbackContext
from telegram_click.decorator import command
from telegram_click.permission import GROUP_ADMIN

@command(name='permission', 
         description='Needs permission',
         permissions=GROUP_ADMIN)
def _permission_command_callback(self, update: Update, context: CallbackContext):

Multiple permissions can be combined using &, | and ~ (not) operators.

If a user does not have permission to use a command it will not be displayed when this user generate a list of commands.

Integrated permission handlers

Custom permission handler

If none of the integrated handlers suit your needs you can simply write your own permission handler by extending the Permission base class and pass an instance of the MyPermission class to the list of permissions:

from telegram import Update
from telegram.ext import CallbackContext
from telegram_click.decorator import command
from telegram_click.permission.base import Permission
from telegram_click.permission import GROUP_ADMIN

class MyPermission(Permission):
    def evaluate(self, update: Update, context: CallbackContext) -> bool:
        from_user = update.effective_message.from_user
        return from_user.id in [12345, 32435]

@command(name='permission', description='Needs permission',
         permissions=MyPermission() & GROUP_ADMIN)
def _permission_command_callback(self, update: Update, context: CallbackContext):

Show "Permission denied" message

By default command calls coming from a user without permission are ignored. If you want to send them a "permission denied" like message you can pass this message to the permission_denied_message argument of the @command decorator.

Targeted commands

Telegram supports the @ notation to target commands at specific bot usernames:

/start               # unspecified
/start@myAwesomeBot  # targeted at self
/start@someOtherBot  # targeted at other bot

When using a MessageHandler instead of a CommandHandler it is possible to catch even commands that are targeted at other bots. By default only messages without a target, and messages that are targeted directly at your bot are processed.

To control this behaviour specify the command_target parameter:

from telegram import Update
from telegram.ext import CallbackContext
from telegram_click.decorator import command
from telegram_click import CommandTarget
from telegram_click.permission import NOBODY

@command(name="commands",
         description="List commands supported by this bot.",
         permissions=NOBODY,
         command_target=CommandTarget.UNSPECIFIED | CommandTarget.SELF)
def _unknown_command_callback(self, update: Update, context: CallbackContext):

You can combine CommandTarget's using logical operators like in the example above.

Error handling

telegram-click automatically handles errors in most situations.

When an exception is raised the user will be notified that his command has crashed the server. By default he will only see a general error message. If you want to send full stacktraces instead, set the print_error parameter to True.

The user is also informed about input errors like

• an argument can not be parsed correctly
• an invalid value is passed for an argument In these cases the user will get a more specific error message and a help message for the command he was trying to use.

Contributing

GitHub is for social coding: if you want to write code, I encourage contributions through pull requests from forks of this repository. Create GitHub tickets for bugs and new features and comment on the ones that you are interested in.

License

telegram-click
Copyright (c) 2019 Markus Ressel

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.