parsidev / telegram-bot-dialog
Telegram Bot API PHP SDK extension that allows to implement dialogs in bots
Requires
- php: ~7.0
- illuminate/support: ~5.5 | ~6.0 | ~7.0
- irazasyed/telegram-bot-sdk: ^3.0
- predis/predis: ~1.0
- symfony/yaml: ~5.0
This package is auto-updated.
Last update: 2024-11-18 22:46:49 UTC
README
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 parsidev/telegram-bot-dialog
Each dialog should be implemented as class that extends basic Dialog as you can see in example bellow:
<?php use BotDialogs\Dialog; /** * Class HelloDialog */ class HelloDialog extends Dialog { // Array with methods that contains logic of dialog steps. // The order in this array defines the sequence of execution. protected $steps = ['hello', 'fine', 'bye']; public function hello() { $this->telegram->sendMessage([ 'chat_id' => $this->getChat()->getId(), 'text' => 'Hello! How are you?' ]); } public function bye() { $this->telegram->sendMessage([ 'chat_id' => $this->getChat()->getId(), 'text' => 'Bye!' ]); $this->jump('hello'); } public function fine() { $this->telegram->sendMessage([ 'chat_id' => $this->getChat()->getId(), 'text' => 'I\'m OK :)' ]); } }
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.
use Telegram\Bot\Commands\Command; use BotDialogs\Dialogs; use App\Dialogs\HelloDialog; class HelloCommand extends Command { /** * @var string Command name */ protected $name = 'hello'; protected $description = 'Just say "Hello" and ask few questions'; /** * @param Dialogs $dialogs */ public function __construct(Dialogs $dialogs) { $this->dialogs = $dialogs; } public function handle($arguments) { $this->dialogs->add(new HelloDialog($this->update)); } }
And code in the webhook controller
use Telegram\Bot\Api; use BotDialogs\Dialogs; // ... public function __construct(Api $telegram, Dialogs $dialogs) { $this->telegram = $telegram; $this->dialogs = $dialogs; } // ... $update = $this->telegram->commandsHandler(true); if (!$this->dialogs->exists($update)) { // Do something if there are no existing dialogs } else { // Call the next step of the dialog $this->dialogs->proceed($update); }
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.
class HelloDialog extends Dialog { protected $steps = [ [ 'name' => 'hello', 'response' => 'Hello my friend!' ], 'fine', 'bye' ]; // ... }
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:
class HelloDialog extends Dialog { protected $steps = [ [ 'name' => 'hello', 'response' => 'Hello my friend! Are you OK?' ], [ 'name' => 'answer', 'is_dich' => true ], 'bye' ]; public function answer() { if ($this->yes) { // Send message "I am fine, thank you!" } elseif ($this->no) { // Send message "No, I am got a sick :(" } } }
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:
class HelloDialog extends Dialog { protected $steps = [ [ 'name' => 'hello', 'response' => 'Hello my friend! Are you OK?' ], [ 'name' => 'answer', 'is_dich' => true, 'yes' => 'fine', 'no' => 'sick', 'default' => 'bye' ], [ 'name' => 'fine', 'response' => 'I am fine, thank you!', 'jump' => 'bye', ], [ 'name' => 'sick', 'response' => 'No, I am got a sick :(', ], 'bye' ]; }
###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 stepproceed()
- Proceed the dialog to the next stepend()
- End dialogjump($step)
- Jump to the particular stepremember($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 dialogget(Telegram\Bot\Objects\Update $update)
- Returns the dialog object for the existing dialogproceed(Telegram\Bot\Objects\Update $update)
- Run the next step handler for the existing dialogexists(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:
'scenarios' => [ HelloDialog::class => base_path('config/dialogs/hello.yml') ],
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