- Регистрация
- 1 Мар 2015
- Сообщения
- 1,481
- Баллы
- 155
Continuing from the , this time I will describe the changes I made to the library.
The user in the Telegram bot can send different types of messages, such as text messages, photos, videos, etc. In some cases, we need to know what type of message the client has sent so that we can respond to it accordingly, or perhaps we need to limit the type of message for the client
So, a method had to be created to detect the type of message sent by the client, and as a result, the message type could be received using the following method:
$type = Bot::message()->type();
The values it returns are one of these:
'text', 'photo', 'video', 'audio', 'document', 'sticker', 'animation', 'location', 'contact', 'poll'
I also put the consts of these types in the message method, which are:
const TYPE_TEXT = 'text';
const TYPE_PHOTO = 'photo';
const TYPE_VIDEO = 'video';
const TYPE_AUDIO = 'audio';
const TYPE_DOCUMENT = 'document';
const TYPE_STICKER = 'sticker';
const TYPE_ANIMATION = 'animation';
const TYPE_LOCATION = 'location';
const TYPE_CONTACT = 'contact';
const TYPE_POLL = 'poll';
const TYPE_MESSAGE = 'message';
These constants are accessible from the Message class, so creating a condition to check the type of user message could look something like this:
if(Bot::message()->type() == Message::TYPE_TEXT){
// Do something.
}
else{
Bot::new()->text('Please send your message as text.')->send();
}
There is another type of message. When the client clicks on an inline button In this case, Telegram sends us a Callback that also contains the data object of that message.
I created the isCallbackQuery method for this purpose, which can be used as follows:
if ( Bot::isCallbackQuery() ) {
$data = Bot::callback()->data();
Bot::new()->text("? Get Callback Query:\nData : $data")->send();
}
So if the value of Bot::isCallbackQuery() is true, we know that the client has clicked a button. In this case, we have access to the callback method and we can get the data of the button that the client clicked using Bot::callback()->data()
View on GitHub:
The user in the Telegram bot can send different types of messages, such as text messages, photos, videos, etc. In some cases, we need to know what type of message the client has sent so that we can respond to it accordingly, or perhaps we need to limit the type of message for the client
So, a method had to be created to detect the type of message sent by the client, and as a result, the message type could be received using the following method:
$type = Bot::message()->type();
The values it returns are one of these:
'text', 'photo', 'video', 'audio', 'document', 'sticker', 'animation', 'location', 'contact', 'poll'
I also put the consts of these types in the message method, which are:
const TYPE_TEXT = 'text';
const TYPE_PHOTO = 'photo';
const TYPE_VIDEO = 'video';
const TYPE_AUDIO = 'audio';
const TYPE_DOCUMENT = 'document';
const TYPE_STICKER = 'sticker';
const TYPE_ANIMATION = 'animation';
const TYPE_LOCATION = 'location';
const TYPE_CONTACT = 'contact';
const TYPE_POLL = 'poll';
const TYPE_MESSAGE = 'message';
These constants are accessible from the Message class, so creating a condition to check the type of user message could look something like this:
if(Bot::message()->type() == Message::TYPE_TEXT){
// Do something.
}
else{
Bot::new()->text('Please send your message as text.')->send();
}
Detecting a query callback in a Telegram bot
There is another type of message. When the client clicks on an inline button In this case, Telegram sends us a Callback that also contains the data object of that message.
I created the isCallbackQuery method for this purpose, which can be used as follows:
if ( Bot::isCallbackQuery() ) {
$data = Bot::callback()->data();
Bot::new()->text("? Get Callback Query:\nData : $data")->send();
}
So if the value of Bot::isCallbackQuery() is true, we know that the client has clicked a button. In this case, we have access to the callback method and we can get the data of the button that the client clicked using Bot::callback()->data()
View on GitHub: