Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedPublicChat with unsafe operator "as"
Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedChannelChat with unsafe operator "as"
Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedChannelChatImpl with unsafe operator "as"
Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedGroupChat with unsafe operator "as"
Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedGroupChatImpl with unsafe operator "as"
Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedSupergroupChat with unsafe operator "as"
Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedSupergroupChatImpl with unsafe operator "as"
Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedPrivateChat with unsafe operator "as"
Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedPrivateChatImpl with unsafe operator "as"
Will cast incoming dev.inmo.tgbotapi.types.chat.ExtendedChat to a ExtendedUser with unsafe operator "as"
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Will use handleLiveLocation with replying to message each time new message will be sent by live location update
Will use handleLiveLocation with replying to message each time new message will be sent by live location update
This method will send content to the chatId as is
This method will send content to the chatId as is
This method will send message content to the chatId. In difference with copyMessage, this method will use native methods for data sending (like dev.inmo.tgbotapi.extensions.api.send.media.sendPhoto if inoming content is dev.inmo.tgbotapi.types.message.content.PhotoContent)
This method will send message content to the chat. In difference with copyMessage, this method will use native methods for data sending (like dev.inmo.tgbotapi.extensions.api.send.media.sendPhoto if inoming content is dev.inmo.tgbotapi.types.message.content.PhotoContent)
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendBotAction request
Will execute sendAnimation request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendAudio request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendContact request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendDice request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendDocument request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendGame request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendInvoice request
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Will execute sendStaticLocation request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendTextMessage request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Will execute sendPhoto request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendRegularPoll request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendQuizPoll request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendSticker request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendLiveLocation request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendVenue request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendVideo request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendVideoNote request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Will execute sendVoice request
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Create UpdateReceiver object which will correctly accumulate updates and send into output updates which INCLUDE dev.inmo.tgbotapi.types.update.MediaGroupUpdates.MediaGroupUpdates.
Use this method to send information about webhook (like url)
Use this method to send information about webhook (like url and certificate)
Config block for preconfiguring of bot HttpClient
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Created by telegramBotWithCustomClientConfig function TelegramBot. This executor will be preconfigured using token and block
Will sendLiveLocation with the first EditLiveLocationInfo data and update than. Each liveTimeMillis passing, the message will be sent again and new edits will be applied to the new message
Will apply Flow.map to the locationsFlow to create EditLiveLocationInfo and pass the result flow to the handleLiveLocation with Flow typed by EditLiveLocationInfo
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some of KeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.replyKeyboard or dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builders for that param
Some InlineKeyboardMarkup. See dev.inmo.tgbotapi.extensions.utils.types.buttons.inlineKeyboard as a builder for that
Allows to create bot using bot urlsKeeper and already prepared client
Allows to create bot using bot urlsKeeper and specify HttpClientEngineFactory by passing clientFactory param and optionally configure it with clientConfig
Allows to create bot using bot urlsKeeper and specify HttpClientEngine by passing clientEngine param and optionally configure HttpClient using clientConfig
Allows to create bot using bot urlsKeeper and specify HttpClientEngine by configuring HttpClient using clientConfig
Allows to create bot using bot token, apiUrl (for custom api servers) and already prepared client
Allows to create bot using bot token and specify HttpClientEngine by passing clientEngine param and optionally configure HttpClient using clientConfig
Allows to create bot using bot token and apiUrl and specify HttpClientEngine by configuring HttpClient using clientConfig
Add STRICT handler to list of available in future BehaviourContextWithFSM. Strict means that for input State will be used State::class == kClass and any State with exactly the same type will pass requirements
Add NON STRICT handler to list of available in future BehaviourContextWithFSM. Non strict means that for input State will be used KClass.isInstance and any inheritor of kClass will pass this requirement
This KClass will be used to compare input State type and declare ability of delegateTo to handle incoming State. See checkHandleable for more info
This flag will be used in checkHandleable to choose strategy of checking incoming State
This handler will be called in case checkHandleable returns true with class caster incoming State in handleState
Check ability of delegateTo to handle this state
When state::class exactly equals to inputKlass will always return true. Otherwise when strict mode is disabled, will be used KClass.isInstance of inputKlass for checking
Handling of state :)
Will be used in case if state handling has not been successfully completed in launchStateHandling
Add NON STRICT handler to list of available in future BehaviourContextWithFSM. Non strict means that for input State will be used KClass.isInstance and any inheritor of kClass will pass this requirement
Add NON STRICT handler to list of available in future BehaviourContextWithFSM. Non strict means that for input State will be used KClass.isInstance and any inheritor of kClass will pass this requirement
Add STRICT handler to list of available in future BehaviourContextWithFSM. Strict means that for input State will be used State::class == kClass and any State with exactly the same type will pass requirements
Use buildBehaviourWithFSM to create BehaviourContextWithFSM and launch getting of updates using longPolling. For longPolling will be used result BehaviourContextWithFSM for both parameters flowsUpdatesFilter and scope
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Use buildBehaviourWithFSM to create BehaviourContextWithFSM and launch getting of updates using longPolling. For longPolling will be used result BehaviourContextWithFSM for both parameters flowsUpdatesFilter and scope
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Creates BehaviourContextWithFSM via creating of DefaultBehaviourContext with this as TelegramBot, scope as target scope for that DefaultBehaviourContext and upstreamUpdatesFlow. Pass statesManager to customize some internal logic of states changes. Pass presetHandlers in case you have some list of BehaviourWithFSMStateHandlerHolder with presets.
!!! WARNING !!! This method WILL NOT call BehaviourContextWithFSM.start of result object and WILL NOT start any updates retrieving. See buildBehaviourWithFSMAndStartLongPolling or telegramBotWithBehaviourAndFSMAndStartLongPolling in case you wish to start longPolling automatically
Creates BehaviourContextWithFSM via creating of DefaultBehaviourContext with this as TelegramBot, scope as target scope for that DefaultBehaviourContext and FlowsUpdatesFilter.allUpdatesFlow of flowUpdatesFilter as DefaultBehaviourContext.upstreamUpdatesFlow. Pass statesManager to customize some internal logic of states changes. Pass presetHandlers in case you have some list of BehaviourWithFSMStateHandlerHolder with presets. Use this method in case you wish to make some additional actions with flowUpdatesFilter.
!!! WARNING !!! This method WILL NOT call BehaviourContextWithFSM.start of result object and WILL NOT start any updates retrieving. See buildBehaviourWithFSMAndStartLongPolling or telegramBotWithBehaviourAndFSMAndStartLongPolling in case you wish to start longPolling automatically
Add NON STRICT handler to list of available in future BehaviourContextWithFSM. Non strict means that for input State will be used KClass.isInstance and any inheritor of kClass will pass this requirement
Add STRICT handler to list of available in future BehaviourContextWithFSM. Strict means that for input State will be used State::class == kClass and any State with exactly the same type will pass requirements
Create bot using telegramBot and start listening for updates using buildBehaviourWithFSMAndStartLongPolling. This method will launch updates retrieving via long polling inside of buildBehaviourWithFSMAndStartLongPolling
Pair of TelegramBot and Job. This Job can be used to stop listening updates in your block you passed here
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Create bot using telegramBot and start listening for updates using buildBehaviourWithFSM. Use this method in case you wish to make some additional actions with flowsUpdatesFilter.
WARNING This method WILL NOT launch any listening of updates. Use something like startGettingOfUpdatesByLongPolling or tools for work with webhooks
Created bot which has been used to create BehaviourContext via buildBehaviourWithFSM
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Use flattenCommandsWithParams and filter out the commands which do not matches to commandRegex
Uses parseCommandsWithArgs on incoming text sources and map them with CommonMessage
Uses parseCommandsWithNamedArgs on incoming text sources and map them with CommonMessage
Uses parseCommandsWithArgsSources on incoming text sources and map them with CommonMessage
If not null, this request will be sent by bot before returning value
If set, this factory will be used to produce requests in case when user have sent incorrect data
If set, this factory will be used to produce requests in case when it is required to say user that chain of scenario has been cancelled
When this trigger returns true, chain is cancelled
It is main param, which will be called on each update. When it return not null, result will be returned as is, but when it returns null, then will be called cancelTrigger (if it will return true - cancelRequestFactory will be called too), errorFactory and then will be returned null
If not null, this request will be sent by bot before returning value
If set, this factory will be used to produce requests in case when user have sent incorrect data
If set, this factory will be used to produce requests in case when it is required to say user that chain of scenario has been cancelled
When this trigger returns true, chain is cancelled
It is main param, which will be called on each update. When it return not null, result will be returned as is, but when it returns null, then will be called cancelTrigger (if it will return true - cancelRequestFactory will be called too), errorFactory and then will be returned null
If not null, this request will be sent by bot before returning value
If set, this factory will be used to produce requests in case when user have sent incorrect data
If set, this factory will be used to produce requests in case when it is required to say user that chain of scenario has been cancelled
When this trigger returns true, chain is cancelled
It is main param, which will be called on each update. When it return not null, result will be returned as is, but when it returns null, then will be called cancelTrigger (if it will return true - cancelRequestFactory will be called too), errorFactory and then will be returned null
If not null, this request will be sent by bot before returning value
If set, this factory will be used to produce requests in case when user have sent incorrect data
If set, this factory will be used to produce requests in case when it is required to say user that chain of scenario has been cancelled
When this trigger returns true, chain is cancelled
It is main param, which will be called on each update. When it return not null, result will be returned as is, but when it returns null, then will be called cancelTrigger (if it will return true - cancelRequestFactory will be called too), errorFactory and then will be returned null
Uses isWithMention passing username as argument to take only messages with username mentions or text mentions
Uses isWithMention passing user as argument to take only messages with user mentions or text mentions
Uses isWithMention passing username as argument to take only messages with username mentions or text mentions
Uses isWithMention passing user as argument to take only messages with user mentions or text mentions
Uses isWithTextMention passing userId as argument to take only messages with userId text mentions
Uses isWithTextMention passing userId as argument to take only messages with userId text mentions
Flat commandsWithParams. Each Pair of BotCommandTextSource and its Array of arg text sources will be associated with its source message
Check, that TextedContent.textSources contains:
Any dev.inmo.tgbotapi.types.message.textsources.MentionTextSource with dev.inmo.tgbotapi.types.message.textsources.MentionTextSource.username equal to username
Any dev.inmo.tgbotapi.types.message.textsources.TextMentionTextSource with dev.inmo.tgbotapi.types.message.textsources.TextMentionTextSource.user with the same username
Uses isWithMention with user (is presented) or isWithTextMention with user to determine user mentioning in this
Check, that TextedContent.textSources contains:
Any dev.inmo.tgbotapi.types.message.textsources.TextMentionTextSource with dev.inmo.tgbotapi.types.message.textsources.TextMentionTextSource.user with the same userId
Subsequent Flow will retrieve only messages without TextContent.textSources which are not BotCommandTextSource
Subsequent Flow will retrieve only messages with ONE BotCommandTextSource. It does not guarantee that this BotCommandTextSource will be at the start of the message
Will filter all the messages and include required commands with commandRegex.
In case you wish to get only the commands at the start of message, use requireCommandAtStart
In case you wish to exclude messages with more than one command, you may use requireSingleCommand
In case you wish to exclude messages with commands params, you may use requireCommandsWithoutParams
Creates cold Flow with the messages with TextedContent where username has been mentioned
Creates cold Flow with the messages with TextedContent where user has been mentioned as text or mentioned with text
Creates cold Flow with the messages with TextedContent where userId has been mentioned with text
Creates cold Flow with the messages with TextedContent where username has been mentioned
Creates cold Flow with the messages with TextedContent where user has been mentioned as text or mentioned with text
Creates cold Flow with the messages with TextedContent where userId has been mentioned with text
This wait will be triggered only for stopped polls and polls, which are sent by the bot
This wait will be triggered only for stopped polls and polls, which are sent by the bot
This wait will be triggered only for stopped polls and polls, which are sent by the bot
Allow only updates from the same user as base CallbackQuery.user
Allow only events from the same chat as base ChatMemberUpdated
Allow only events from the same chat as base ChatMemberUpdated
Allow only messages which are not MediaGroupMessage
Allow only updates from the same user as base InlineQuery.from
Allow only events from the same chat as base Message
Allow only messages which are not in some forum
Allow only updates from the same user as base ShippingQuery.user
Allow only updates from the same user as base ShippingQuery.user
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
Default is InlineQueryFilterByUser]. This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
Default is InlineQueryFilterByUser]. This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Please, remember that your bot must have can_invite_users to receive these requests
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Will be used with initialFilter as initialFilter for upstream onDataCallbackQuery to filter DataCallbackQuery with DataCallbackQuery.data to dataRegex
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Will be converted to Regex via its constructor and pass it to upstream onDataCallbackQuery
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Will be used with initialFilter as initialFilter for upstream onInlineMessageIdDataCallbackQuery to filter InlineMessageIdDataCallbackQuery with InlineMessageIdDataCallbackQuery.data to dataRegex
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Will be converted to Regex via its constructor and pass it to upstream onInlineMessageIdDataCallbackQuery
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
Default is InlineQueryFilterByUser]. This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Will be used with initialFilter as initialFilter for upstream onMessageDataCallbackQuery to filter MessageDataCallbackQuery with MessageDataCallbackQuery.data to dataRegex
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Will be converted to Regex via its constructor and pass it to upstream onMessageDataCallbackQuery
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Please, remember that you must answer to this type of queries using something like dev.inmo.tgbotapi.extensions.api.answers.payments.answerPreCheckoutQueryOk or dev.inmo.tgbotapi.extensions.api.answers.payments.answerPreCheckoutQueryError
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Please, remember that you must answer to this type of queries using something like dev.inmo.tgbotapi.extensions.api.answers.payments.answerShippingQueryOk or dev.inmo.tgbotapi.extensions.api.answers.payments.answerShippingQueryError
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Please, remember that SuccessfulPaymentEvent will be retrieved only in case you will correctly handle dev.inmo.tgbotapi.types.payments.PreCheckoutQuery (via onPreCheckoutQuery, for example)
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
This filter will be called to remove unnecessary data BEFORE scenarioReceiver call
This filter will be applied to each update inside of scenarioReceiver. For example, this filter will be used if you will call dev.inmo.tgbotapi.extensions.behaviour_builder.expectations.waitContentMessage. Use dev.inmo.tgbotapi.extensions.behaviour_builder.BehaviourContextAndTwoTypesReceiver function to create your own. Use dev.inmo.tgbotapi.extensions.behaviour_builder.utils.plus or dev.inmo.tgbotapi.extensions.behaviour_builder.utils.times to combinate several filters
Will be used to identify different "stream". scenarioReceiver will be called synchronously in one "stream". Output of markerFactory will be used as a key for "stream"
Main callback which will be used to handle incoming data if initialFilter will pass that data
Use this extension when you want to follow LiveLocation until it will became StaticLocation. This method is synchronous. You may use something like kotlinx.coroutines.launch or kotlinx.coroutines.async to run it asynchronously
SimpleFilter which will return true in case when all the items in incoming data passed this filter
SimpleFilter which will return true in case when there is any item in incoming data passed this filter
SimpleFilter which will return true in case when there is no any item in incoming data passed this filter
Makes an OR (||) operation between this and other
When both arguments are null, TrueSimpleFilter will be returned
Makes an AND (&&) operation between this and other
When both arguments are null, TrueSimpleFilter will be returned
This parameter will be used to subscribe on different types of update
Will be used for creating of some subscriptions inside of methods, updates listening and different other things in context of working with CoroutineScope and coroutines.
Will be used for creating of some subscriptions inside of methods, updates listening and different other things in context of working with CoroutineScope and coroutines.
Use this method to build bot behaviour and run it via long polling. In case you wish to get FlowsUpdatesFilter for additional manipulations, you must provide external FlowsUpdatesFilter in other buildBehaviour function.
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Use this method in case you wish to make some additional actions with flowUpdatesFilter.
WARNING This method WILL NOT launch any listening of updates. Use something like startGettingOfUpdatesByLongPolling or tools for work with webhooks
Creates new one BehaviourContext using createSubContext and launches behaviourContextReceiver in a new context using doInContext
TRUE BY DEFAULT
Creates new BehaviourContext using its BehaviourContext.copy method
This param will not be used anymore
This function is used in buildBehaviour extensions to provide default CoroutineScope and allow to avoid all unnecessary parameters except of block
Launch behaviourContextReceiver in context of this as BehaviourContext and as kotlin.coroutines.CoroutineContext
FALSE BY DEFAULT. Will stop this in case if passed true
This method will cancel ALL subsequent contexts, expectations and waiters
Create bot using telegramBot and start listening for updates using buildBehaviourWithLongPolling. Use this method in case you wish to make some additional actions with flowsUpdatesFilter.
WARNING This method WILL launch updates listening inside of calling buildBehaviourWithLongPolling
Pair of TelegramBot and Job. This Job can be used to stop listening updates in your block you passed here
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Create bot using telegramBot and start listening for updates using buildBehaviour. Use this method in case you wish to make some additional actions with flowsUpdatesFilter.
WARNING This method WILL NOT launch any listening of updates. Use something like startGettingOfUpdatesByLongPolling or tools for work with webhooks
Created bot which has been used to create BehaviourContext via buildBehaviour
Period in Seconds
Full list of TextSources
Full list of TextSources
Unsafe execution of incoming request. Can throw almost any exception. So, it is better to use something like dev.inmo.tgbotapi.extensions.utils.shortcuts.executeAsync or dev.inmo.tgbotapi.extensions.utils.shortcuts.executeUnsafe
Amount of DefaultKtorRequestsExecutor which will be created and used under the hood
Unsafe execution of incoming request. Can throw almost any exception. So, it is better to use something like dev.inmo.tgbotapi.extensions.utils.shortcuts.executeAsync or dev.inmo.tgbotapi.extensions.utils.shortcuts.executeUnsafe
Will always be called after potentialFactory has tried to make request and got some result. If returns value - that value will be returned from dev.inmo.tgbotapi.bot.RequestsExecutor.execute instead
Will always be called before potentialFactory will try to make request
Will always be called before requests executor will check all callsFactories for an opportunity to make call of request
Will be called when any exception will happen due to the request handling. If returns value - that value will be returned from dev.inmo.tgbotapi.bot.RequestsExecutor.execute instead
Will be called when there is no KtorCallFactory from callsFactories which may handle request. If returns value - that value will be returned from dev.inmo.tgbotapi.bot.RequestsExecutor.execute instead
Will be called when resultCallFactory is the KtorCallFactory from callsFactories which has successfully handled request and returned result. If returns value - that value will be returned from dev.inmo.tgbotapi.bot.RequestsExecutor.execute instead
This step will be called when the result has been retrieved (or exception has happened). If returns value - that value will be returned from dev.inmo.tgbotapi.bot.RequestsExecutor.execute instead
Shortcut for telegramBot
Will be called with each item from tokens in process of bots creation
It is strategy by which the bot is selected for the execution. This lambda will receive -1 when request execution just started and this call is first in context of one execute. By default, will select next TelegramBot when called (or first when current index is last or -1)
Bots which will be used to executes
It is strategy by which the bot is selected for the execution. This lambda will receive -1 when request execution just started and this call is first in context of one execute. By default, will select next TelegramBot when called (or first when current index is last or -1)
Unsafe execution of incoming request. Can throw almost any exception. So, it is better to use something like dev.inmo.tgbotapi.extensions.utils.shortcuts.executeAsync or dev.inmo.tgbotapi.extensions.utils.shortcuts.executeUnsafe
Pairs with first parameter as a token and second parameter api url. Will be used to create result SimpleMultiServerRequestsExecutor.bots
Will be called with each item from tokens in process of bots creation
It is strategy by which the bot is selected for the execution. This lambda will receive -1 when request execution just started and this call is first in context of one SimpleMultiServerRequestsExecutor.execute. By default, will select next TelegramBot when called (or first when current index is last or -1)
This method will be called inside of SimpleMultiServerRequestsExecutor.close method. By default, will close all SimpleMultiServerRequestsExecutor.bots
Unsafe execution of incoming request. Can throw almost any exception. So, it is better to use something like dev.inmo.tgbotapi.extensions.utils.shortcuts.executeAsync or dev.inmo.tgbotapi.extensions.utils.shortcuts.executeUnsafe
Creates MultipartFile based on incoming MPPFile (common File in java, for example)
Creates MultipartFile based on incoming filename and inputSource
dev.inmo.tgbotapi.webapps.WebAppInitData.queryId
dev.inmo.tgbotapi.webapps.WebAppInitData.queryId
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Disables automatic server-side content type detection for document
Full list of TextSources
Use this method to send general files. On success, the sent ContentMessage with DocumentContent is returned. Bots can currently send files of any type of up to 50 MB in size, this limit may be changed in the future.
Disables automatic server-side content type detection for document
Use this method to be sure that you are correctly sending documents media group
Full list of TextSources
Use this method to be sure that you are correctly sending playlist with audios
Full list of TextSources
Use this method to be sure that you are correctly sending visual media group
Full list of TextSources
JSON-ENCODED FIELD
JSON-ENCODED FIELD
JSON-ENCODED FIELD
JSON-ENCODED FIELD
Full list of TextSources
SendPoll in case when all is right. It can return SendRegularPoll for QuizPoll in case if QuizPoll.correctOptionId equal to null
Full list of TextSources
Period in Seconds
Full list of TextSources
Will create one of CreateNewStickerSet types based on the first element of stickers
Will be used only if you are creating custom emojis sticker pack (by passing stickers with type InputSticker.WithKeywords.CustomEmoji)
Use this method to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified url, containing a JSON-serialized Update.
If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the url, e.g. https://www.example.com/
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Period in Seconds
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Period in Seconds
Represents the InputMessageContent of a text message to be sent as the result of an inline query.
Full list of TextSources
The source User of this type
The source User of this type
The source User of this type
You will receive this data in dev.inmo.tgbotapi.types.queries.callback.DataCallbackQuery.data field
Creates CallbackDataInlineKeyboardButton
Creates CallbackGameInlineKeyboardButton
Creates SwitchInlineQueryCurrentChatInlineKeyboardButton
Creates LoginURLInlineKeyboardButton
Creates PayInlineKeyboardButton
Creates URLInlineKeyboardButton
Creates WebAppInlineKeyboardButton. Please, remember that this button is available in private chats only
Creates RequestUserKeyboardButton with KeyboardButtonRequestUser.Bot
Creates RequestChatKeyboardButton with KeyboardButtonRequestChat.Channel
Creates RequestChatKeyboardButton with KeyboardButtonRequestChat.Group
Creates RequestChatKeyboardButton
Creates RequestChatKeyboardButton with KeyboardButtonRequestChat
Creates RequestContactKeyboardButton
Creates RequestLocationKeyboardButton
Creates RequestPollKeyboardButton
Creates RequestUserKeyboardButton with KeyboardButtonRequestUser.Any
Creates RequestUserKeyboardButton
Creates RequestUserKeyboardButton with KeyboardButtonRequestUser.Common
Creates SimpleKeyboardButton
Creates WebAppKeyboardButton
Crutch due to the fact that direct serialization of objects currently does not work perfectly
Returns a representation of an immutable list of all enum entries, in the order they're declared.
This method may be used to iterate over the enum entries.
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
if this enum type has no constant with the specified name
Returns an array containing the constants of this enum type, in the order they're declared.
This method may be used to iterate over the constants.
Copying current instance as ChatPermissions, but realizations of this interface may differently override this method
Copying current instance as ChatPermissions, but realizations of this interface may differently override this method
This field represents field "has_aggressive_anti_spam_enabled" from API
This field represents field "join_by_request" from API
This field represents field "join_to_send_messages" from API
This field represents field "has_aggressive_anti_spam_enabled" from API
This field represents field "join_by_request" from API
This field represents field "join_to_send_messages" from API
This field represents field "has_aggressive_anti_spam_enabled" from API
This field represents field "join_by_request" from API
This field represents field "join_to_send_messages" from API
Full list of TextSources
Period in Seconds
Full list of TextSources
Full list of TextSources
Disables automatic server-side content type detection for files uploaded using multipart/form-data. Always used by Telegram system as true, if the document is sent as part of an album.
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Full list of TextSources
Without leading "/"
Without sharp (#)
Without sharp (#)
Without leading "@"
This method will prepare TextSources list for messages. Remember, that first part will be separated with captionLength and all others with
This method will prepare TextSources list for messages with textLength
This method will prepare TextSources list for messages. Remember, that first part will be separated with captionLength and all others with
This method will prepare TextSources list for messages with textLength
This variable respects to default parse mode used in places like next:
dev.inmo.tgbotapi.types.message.content.TextContent.createResends
Nullable due to documentation (https://core.telegram.org/bots/api#poll)
Full list of TextSources
The source User of this type
The source User of this type
The source User of this type
The source User of this type
The source User of this type
The source User of this type
Creates DefaultFlowsUpdatesFilter
Default realization of KSLog which will be used everywhere where there is no some custom variant of KSLog
By default, uses TagLogger with tag KTgBot (which in fact falling back to KSLog.default with KTgBot default tag)
New immutable list which will be deattached from this builder
It is not safe field which contains potentially changeable List
Data from dev.inmo.tgbotapi.webapps.WebApp.initData
Data from dev.inmo.tgbotapi.webapps.WebApp.initDataUnsafe from the field dev.inmo.tgbotapi.webapps.WebAppInitData.hash
Add bold using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.bold
Add bold using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.bold. Will reuse separator config from buildEntities
Version of EntitiesBuilder.bold with new line at the end
Version of EntitiesBuilder.bold with new line at the end. Will reuse separator config from buildEntities
Add botCommand using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.botCommand
Version of EntitiesBuilder.botCommand with new line at the end
Add cashTag using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.cashTag
Add cashTag using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.cashTag. Will reuse separator config from buildEntities
Version of EntitiesBuilder.cashTag with new line at the end
Version of EntitiesBuilder.cashTag with new line at the end. Will reuse separator config from buildEntities
Add code using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.code
Version of EntitiesBuilder.code with new line at the end
Add customEmoji using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.customEmoji
Add customEmoji using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.customEmoji. Will reuse separator config from buildEntities
Version of EntitiesBuilder.customEmoji with new line at the end
Version of EntitiesBuilder.customEmoji with new line at the end. Will reuse separator config from buildEntities
Add email using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.email
Add email using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.email. Will reuse separator config from buildEntities
Version of EntitiesBuilder.email with new line at the end
Version of EntitiesBuilder.email with new line at the end. Will reuse separator config from buildEntities
Add hashtag using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.hashtag
Add hashtag using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.hashtag. Will reuse separator config from buildEntities
Version of EntitiesBuilder.hashtag with new line at the end
Version of EntitiesBuilder.hashtag with new line at the end. Will reuse separator config from buildEntities
Add italic using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.italic
Add italic using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.italic. Will reuse separator config from buildEntities
Version of EntitiesBuilder.italic with new line at the end
Version of EntitiesBuilder.italic with new line at the end. Will reuse separator config from buildEntities
Add link using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.link
Version of EntitiesBuilder.link with new line at the end
Add mention using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.mention
Add mention using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.mention. Will reuse separator config from buildEntities
Version of EntitiesBuilder.mention with new line at the end
Version of EntitiesBuilder.mention with new line at the end. Will reuse separator config from buildEntities
Add phone using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.phone
Add phone using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.phone. Will reuse separator config from buildEntities
Version of EntitiesBuilder.phone with new line at the end
Version of EntitiesBuilder.phone with new line at the end. Will reuse separator config from buildEntities
Add pre using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.pre
Version of EntitiesBuilder.pre with new line at the end
Will add simple dev.inmo.tgbotapi.types.message.textsources.regular
Will add simple dev.inmo.tgbotapi.types.message.textsources.regular and "\n" at the end
Add spoiler using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.spoiler
Add spoiler using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.spoiler. Will reuse separator config from buildEntities
Version of EntitiesBuilder.spoiler with new line at the end
Version of EntitiesBuilder.spoiler with new line at the end. Will reuse separator config from buildEntities
Add strikethrough using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.strikethrough
Add strikethrough using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.strikethrough. Will reuse separator config from buildEntities
Version of EntitiesBuilder.strikethrough with new line at the end
Version of EntitiesBuilder.strikethrough with new line at the end. Will reuse separator config from buildEntities
Add underline using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.underline
Add underline using EntitiesBuilder.add with dev.inmo.tgbotapi.types.message.textsources.underline. Will reuse separator config from buildEntities
Version of EntitiesBuilder.underline with new line at the end
Version of EntitiesBuilder.underline with new line at the end. Will reuse separator config from buildEntities
Replaced
import dev.inmo.tgbotapi.extensions.utils.extensions.TelegramBotCommandsDefaults
TelegramBotCommandsDefaults.defaultArgsSeparatorRegexParse text sources to find commands with their arguments. This method will skip all the text sources before first command and all following text sources until the next command will be guessed as an args of last found command
Parse commands and their args. Logic will find command, get all subsequent data as args until new command
Uses parseCommandsWithArgs to create base argsSeparator split args for commands and map their as k-v pairs. Sample:
/command args1=value1 arg2=value2 arg1=value3Will produce Map with one key command and the list of three pairs:
args1 to value1
args2 to value2
args1 to value3
Array of named arguments
Renamed
import dev.inmo.tgbotapi.extensions.utils.extensions.parseCommandsWithArgs
parseCommandsWithArgs(argsSeparator)Parse commands and their args. Logic will find command, get all subsequent data as args until new command
true in case if this message is from the same chat (with id == chatId) and this equal messageId identifier
true in case if this message is from the same chat and this equal messageId identifier
true in case if this message is the same as other. The same here means that these messages from one chat and have equal Message.messageId identifier
Thread is the same thing that topic
true in case if this message is in the chat chatId and topic threadId. The same here means that these messages from one chat and have equal Message.threadIdOrNull identifier
Thread is the same thing that topic
true in case if this message is from the chat and topic threadId. The same here means that these messages from one chat and have equal Message.threadIdOrNull identifier
Thread is the same thing that topic
true in case if this message is in the same topic as the other. The same here means that these messages from one chat and have equal Message.threadIdOrNull identifier
Thread is the same thing that topic
true in case if this message is in the chat chatId and topic threadId. The same here means that these messages from one chat and have equal Message.threadIdOrNull identifier
Thread is the same thing that topic
true in case if this message is from the chat and topic threadId. The same here means that these messages from one chat and have equal Message.threadIdOrNull identifier
Thread is the same thing that topic
true in case if this message is from the same chat and topic as other. The same here means that these messages from one chat and have equal Message.threadIdOrNull identifier
Link which can be used as by any user to get access to Message. Returns null in case when there are no known way to build link (for PrivateChats, for example)
Crutch for support of strikethrough in default markdown. Simply add modifier, but it will not look like correct
Crutch for support of underline in default markdown. Simply add modifier, but it will not look like correct
Convert incoming dev.inmo.tgbotapi.types.message.abstracts.ContentMessage.content of messages with fullEntitiesList and check that incoming message contains BotCommandTextSource. Besides, it is checking that BotCommandTextSource.command with incoming commandRegex
The same message in case if it contains somewhere in text BotCommandTextSource with Regex.matches
Convert incoming dev.inmo.tgbotapi.types.message.abstracts.ContentMessage.content of messages with fullEntitiesList and check that incoming message contains first TextSource as BotCommandTextSource. Besides, it is checking that BotCommandTextSource.command with incoming commandRegex and for other TextSource objects used next rules: all incoming text sources will be passed as is, RegularTextSource will be split by " " for several RegularTextSource which will contains not empty args without spaces.
Paired original message and converted list with first entity BotCommandTextSource and than all others according to rules in description
This parameter is required when you want to include textMessages for channels too. In this case will be created new channel which will aggregate messages from FlowsUpdatesFilter.messagesFlow and FlowsUpdatesFilter.channelPostsFlow. In case it is null will be used Flows mapping
Convert incoming dev.inmo.tgbotapi.types.message.abstracts.ContentMessage.content of messages with fullEntitiesList and check that incoming message contains ONLY ONE TextSource and that is BotCommandTextSource. Besides, it is checking that BotCommandTextSource.command with incoming commandRegex
The same message in case if it contains only BotCommandTextSource with Regex.matches
Shortcut for photoMessages
Creates InlineKeyboardMarkup using internal matrix
Factory-function for InlineKeyboardBuilder, but in difference with inlineKeyboard this function will create single-row inline keyboard
Factory-function for ReplyKeyboardBuilder, but in difference with replyKeyboard this method will create single-row keyboard
Factory-function for InlineKeyboardBuilder. It will apply to internally created InlineKeyboardMarkup and InlineKeyboardBuilder.build then
Creates and put SwitchInlineQueryChosenChatInlineKeyboardButton
Creates and put SwitchInlineQueryCurrentChatInlineKeyboardButton
Factory-function for ReplyKeyboardBuilder. It will apply to internally created ReplyKeyboardMarkup and ReplyKeyboardBuilder.build then
Creates and put RequestUserKeyboardButton with KeyboardButtonRequestUser.Bot
Creates and put RequestChatKeyboardButton with KeyboardButtonRequestChat.Channel
Creates and put RequestChatKeyboardButton
Creates and put RequestChatKeyboardButton with KeyboardButtonRequestChat
Creates and put RequestChatKeyboardButton with KeyboardButtonRequestChat.Group
Creates and put RequestPollKeyboardButton
Creates and put RequestUserKeyboardButton
Creates and put RequestUserKeyboardButton with KeyboardButtonRequestUser.Common
Creates and put RequestUserKeyboardButton with KeyboardButtonRequestUser.Any
Creates and put WebAppInlineKeyboardButton. Please, remember that this button is available in private chats only
Creates and put WebAppKeyboardButton
kotlinx.coroutines.flow.Flow which will emit updates to the collector while they will be accumulated. Works the same as longPollingFlow, but it will cancel the flow after the first one HttpRequestTimeoutException
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Allows to include webhook in custom route everywhere in your server
Will be used for mapping of media groups
Pass this parameter to set custom exception handler for getting updates
Some receiver block like dev.inmo.tgbotapi.updateshandlers.FlowsUpdatesFilter
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Will startGettingOfUpdatesByLongPolling using incoming updatesFilter. It is assumed that you ALREADY CONFIGURE all updates receivers, because this method will trigger getting of updates and.
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Will enable longPolling by creating FlowsUpdatesFilter with flowsUpdatesFilterUpdatesKeeperCount as an argument and applied flowUpdatesPreset. It is assumed that you WILL CONFIGURE all updates receivers in flowUpdatesPreset, because of after flowUpdatesPreset method calling will be triggered getting of updates.
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Setting up ktor server, set webhook info via SetWebhookRequest request.
port which will be listen by bot
address to listen by bot
Scope which will be used for
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Setting up ktor server
port which will be listen by bot
address to listen by bot. If null - will be set up in root of host
Scope which will be used for
If configured - server will be created with sslConnector. connector will be used otherwise
Will be used for calling of updateHandlerWithMediaGroupsAdaptation. Pass null in case you wish to enable classic way of updates handling, but in that mode some media group messages can be retrieved in different updates
Create UpdateReceiver object which will correctly accumulate updates and send into output updates which INCLUDE dev.inmo.tgbotapi.types.update.MediaGroupUpdates.MediaGroupUpdates.
Will map incoming BaseSentMessageUpdates to CommonMessage from BaseSentMessageUpdate.data
Will map incoming BaseSentMessageUpdates to ContentMessage from BaseSentMessageUpdate.data
New Flow with DataCallbackQuery type, got from CallbackQueryUpdate.data field
New Flow with GameShortNameCallbackQuery type, got from CallbackQueryUpdate.data field
New Flow with UnknownCallbackQueryType type, got from CallbackQueryUpdate.data field
Will map incoming BaseSentMessageUpdates to UnknownMessageType from BaseSentMessageUpdate.data
Will convert incoming list of Updates to list with Updates, which include dev.inmo.tgbotapi.types.message.abstracts.ContentMessages with dev.inmo.tgbotapi.types.message.content.MediaGroupContent
Flow.filter incoming BaseMessageUpdates by their IdChatIdentifier
Flow.filter incoming BaseMessageUpdates by their IdChatIdentifier using Chat.id of chat
Convert incoming dev.inmo.tgbotapi.types.message.abstracts.ContentMessage.content of messages with fullEntitiesList and check that incoming message contains BotCommandTextSource. Besides, it is checking that BotCommandTextSource.command with incoming commandRegex
The same message in case if it contains somewhere in text BotCommandTextSource with Regex.matches
Convert incoming dev.inmo.tgbotapi.types.message.abstracts.ContentMessage.content of messages with fullEntitiesList and check that incoming message contains first TextSource as BotCommandTextSource. Besides, it is checking that BotCommandTextSource.command with incoming commandRegex and for other TextSource objects used next rules: all incoming text sources will be passed as is, RegularTextSource will be split by " " for several RegularTextSource which will contains not empty args without spaces.
Paired original message and converted list with first entity BotCommandTextSource and than all others according to rules in description
Convert incoming dev.inmo.tgbotapi.types.message.abstracts.ContentMessage.content of messages with fullEntitiesList and check that incoming message contains ONLY ONE TextSource and that is BotCommandTextSource. Besides, it is checking that BotCommandTextSource.command with incoming commandRegex
The same message in case if it contains only BotCommandTextSource with Regex.matches
Non-suspendable function for easy-to-use creating of FlowsUpdatesFilter and applying the block to it
A predicate to test that message has been sent in the forum. Use it as the initialFilter parameter in behaviour builder triggers. E.g.
onContentMessage(
initialFilter = Message::forumMessage
) {
// The message here will be from forum
}true if this Message is from forum (threadIdOrNull is not null). False otherwise.
A predicate to test whether a message contains any commands in its body. Use it as the initialFilter parameter in behaviour builder triggers. E.g.
onContentMessage(
initialFilter = CommonMessage<MessageContent>::hasCommands
) {
// the message contains at least one command here
}true if this CommonMessage contains any commands. False otherwise.
A predicate to test whether a message contains any commands in its body. Use it as the initialFilter parameter in behaviour builder triggers. E.g.
onContentMessage(
initialFilter = CommonMessage<MessageContent>::hasNoCommands
) {
// the message contains no commands here
}true if this CommonMessage does not contain any commands. False otherwise.
A predicate to test that message has not been sent in the forum. Use it as the initialFilter parameter in behaviour builder triggers. E.g.
onContentMessage(
initialFilter = Message::notForumMessage
) {
// The message here will not be from forum
}true if this Message is not from forum (threadIdOrNull is not null). False otherwise.
Mapped Flow with Pairs. Pair.first in this pair will be UpdateIdentifier. It could be useful in cases you are using InlineQueryUpdate.updateId for some reasons. Pair.second will always be BaseChosenInlineResult.
Filter updates only with BaseChosenInlineResult and map it to a Flow with values BaseChosenInlineResult
Mapped Flow with Pairs. Pair.first in this pair will be UpdateIdentifier. It could be useful in cases you are using InlineQueryUpdate.updateId for some reasons. Pair.second will always be BaseInlineQuery.
Filter updates only with BaseInlineQuery and map it to a Flow with values BaseInlineQuery
Converts flow to Flow of BaseSentMessageUpdate
Mapped Flow with Pairs. Pair.first in this pair will be UpdateIdentifier. It could be useful in cases you are using InlineQueryUpdate.updateId for some reasons. Pair.second will always be LocationChosenInlineResult.
Filter updates only with LocationChosenInlineResult and map it to a Flow with values LocationChosenInlineResult
Mapped Flow with Pairs. Pair.first in this pair will be UpdateIdentifier. It could be useful in cases you are using InlineQueryUpdate.updateId for some reasons. Pair.second will always be LocationInlineQuery.
Filter updates only with LocationInlineQuery and map it to a Flow with values LocationInlineQuery
Converts flow to Flow of BaseSentMessageUpdate
Deserialize source as dev.inmo.tgbotapi.types.update.abstracts.Update
Deserialize this as dev.inmo.tgbotapi.types.update.abstracts.Update. In fact, it is must be JSON
Deserialize this as dev.inmo.tgbotapi.types.update.abstracts.Update
Returns a representation of an immutable list of all enum entries, in the order they're declared.
This method may be used to iterate over the enum entries.
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
if this enum type has no constant with the specified name
Returns an array containing the constants of this enum type, in the order they're declared.
This method may be used to iterate over the constants.
Analog of merge function for Flows. The difference is in the usage of BroadcastChannel in this case
First SlotMachineReelImage with SlotMachineReelImage.number equal to receiver OR SlotMachineReelImage.SEVEN
First SlotMachineReelImage with SlotMachineReelImage.text equal to receiver OR SlotMachineReelImage.SEVEN
Shortcut for onlyCommonMessages
Simple factory to convert ContentMessage to a CommonMessage
Filter the messages and checking that incoming CommonMessage is PossiblySentViaBotCommonMessage and its PossiblySentViaBotCommonMessage.senderBot is not null
Filter the messages and checking that incoming ContentMessage.content is not MediaGroupContent
Filter the messages and checking that incoming CommonMessage not is PossiblySentViaBotCommonMessage or its PossiblySentViaBotCommonMessage.senderBot is null
Returns a representation of an immutable list of all enum entries, in the order they're declared.
This method may be used to iterate over the enum entries.
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
if this enum type has no constant with the specified name
Returns an array containing the constants of this enum type, in the order they're declared.
This method may be used to iterate over the constants.
Should return the data which must be used in WebApp.sendData. If returns null, data will not be sent
In case if WebAppInitData.queryId is presented in WebApp.initDataUnsafe, will be called that callback. Before and after calling of this callback will not be used any method of answering to the telegram system, so, you must use something like answerWebAppQuery by yourself to send the result
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
The callback which should be used in case you want to turn off events handling
Should return the data which must be used in WebApp.sendData. If returns null, data will not be sent
In case if WebAppInitData.queryId is presented in WebApp.initDataUnsafe, will be called that callback. Before and after calling of this callback will not be used any method of answering to the telegram system, so, you must use something like answerWebAppQuery by yourself to send the result
