Download the PHP package zarincheg/telegram-bot-dialogs without Composer

telegram-bot-dialogs

The extension for Telegram Bot API PHP SDK that allows to implement dialogs in bots

This libriary allows to make simple dialogs for your Telegram bots that based on the Telegram Bot API - PHP SDK (https://github.com/irazasyed/telegram-bot-sdk).

Installation

You can easy install the package using Composer:

composer require zarincheg/telegram-bot-dialogs dev-master

After that you need to register the service provide for using with Laravel DI container Open config/app.php and, to your providers array at the bottom, add:

Each dialog should be implemented as class that extends basic Dialog as you can see in example bellow:

For initiate new dialog you have to use Dialogs class instance to add new dialog implementation. And for execute the first and next steps you have to call Dialogs::procceed() mehod with update object as an argument. Also it is possible to use dialogs with Telegram commands and DI through type hinting.

And code in the webhook controller

For storing dialog information(also for the data that pushed by the Dialog::remember() method) using Redis.

Advanced definition of the dialog steps

You can define default text answers for your dialog steps. For this you have to define the step as an array with name and response fields.

In this case, if you don't need any logic inside the step handler - you can don't define it. Just put the response inside the step definition. It works good for welcome messages, messages with tips/advices and so on. If you want format response with markdown, just set markdown field to true.

Also, you can control dialog direction in step by defining jump and end fields. jump acts as jump() method - dialog jumps to particular step. end field, is set to true, ends dialog after current step.

Also, you can use is_dich (is it a dichotomous question) option of the step. If this option set to true, you can use yes and no fields of the Dialog instance to check user answer. For example:

In the config/dialogs.php you can modify aliases for yes/no meanings.

Often in dichotomous question you only need to send response and jump to another step. In this case, you can define steps with responses and set their names as values of 'yes', 'no' or 'default' keys of dichotomous step. For example:

Access control with in dialogs

You can inherit AuthorizedDialog class and put Telegram usernames into $allowedUsers property. After that just for users in the list will be allowed to start the dialog.

Available methods of the Dialog class

• start() - Start the dialog from the first step
• proceed() - Proceed the dialog to the next step
• end() - End dialog
• jump($step) - Jump to the particular step
• remember($value) - Remember some information for the next step usage (For now just a "short" memory works, just for one step)
• isEnd() - Check the end of the dialog

Available methods of the Dialogs class

• add(Dialog $dialog) - Add the new dialog
• get(Telegram\Bot\Objects\Update $update) - Returns the dialog object for the existing dialog
• proceed(Telegram\Bot\Objects\Update $update) - Run the next step handler for the existing dialog
• exists(Telegram\Bot\Objects\Update $update) - Check for existsing dialog

Steps configuration in separate files

You can define dialog configuration in separate yaml or php files. To do this, set scenarios in dialogs configuration file, using dialog class name as key and path to config file as value, for example:

Configuration from files in production environment stored in default cache instanse. Because of this, you shall add php artisan cache:clear to your deployment script.

What is planned to improve:

• Refactor for using names in Dialogs::add() instead of objects and rename to start()
• Add LUIS API support (https://www.luis.ai/)
• Long-term memory