Update parsing
Certain updates may have text payload that can be parsed for further processing. Let's take a look at them:
-
MessageUpdate->message.text -
EditedMessageUpdate->editedMessage.text -
ChannelPostUpdate->channelPost.text -
EditedChannelPostUpdate->editedChannelPost.text -
InlineQueryUpdate->inlineQuery.query -
ChosenInlineResultUpdate->chosenInlineResult.query -
CallbackQueryUpdate->callbackQuery.data -
ShippingQueryUpdate->shippingQuery.invoicePayload -
PreCheckoutQueryUpdate->preCheckoutQuery.invoicePayload -
PollUpdate->poll.question -
PurchasedPaidMediaUpdate->purchasedPaidMedia.paidMediaPayload
From the listed updates, a certain parameter is selected and taken as TextReference, for further parsing.
The selected parameters are parsed with the appropriate configured delimiters into the command and parameters to it.
See configuration commandParsing block.
You can see in the diagram below which components are mapped to which parts of the target function.
There is also an annotation called @ParamMapping for convenience or for any special case.
It allows you to map the name of the parameter from the incoming text to any parameter.
This is also convenient when your incoming data is limited, for example, CallbackData (64 characters).
See example of usage:
greeting?name=Adam
@CommandHandler(["greeting"])
suspend fun greeting(@ParamMapping("name") anyParameterName: String, user: User, bot: TelegramBot) {
message { "Hello, $anyParameterName" }.send(to = user, via = bot)
}And also it can be used for catching unnamed parameters, in cases where the parser is set up such that parameter names are skipped or even they absent, which passes by 'param_n' pattern, where n is its ordinal.
For example such text - myCommand?p1=v1&v2&p3=&p4=v4&p5=, will be parsed to:
- command -
myCommand - parameters
-
p1=v1 -
param_2=v2 -
p3= `` -
p4=v4 -
p5= ``
-
As you can see since second parameter don't have declared name it represented as param_2.
So you can abbreviate the variable names in the callback itself and use clear readable names in the code.
Considering the information from above if you expect deeplink in your start command you can catch it with:
@CommandHandler(["/start"])
suspend fun start(@ParamMapping("param_1") deeplink: String?, user: User, bot: TelegramBot) {
message { "deeplink is $deeplink" }.send(to = user, via = bot)
}In commandParsing configuration we have parameter useIdentifierInGroupCommands when it turned on, we can use TelegramBot.identifier (don't forget to change it if you are using described parameter) in the command matching process, it helps to separate similar commands between several bots, otherwise the @MyBot part will just be skipped.