tgbotapi.behaviour_builder/dev.inmo.tgbotapi.extensions.behaviour_builder.triggers_handling/onLocationInlineQuery

onLocationInlineQuery

suspend fun <BC : BehaviourContext> BC.onLocationInlineQuery(initialFilter: SimpleFilter<LocationInlineQuery>? = null, subcontextUpdatesFilter: CustomBehaviourContextAndTwoTypesReceiver<BC, Boolean, LocationInlineQuery, Update>? = InlineQueryFilterByUser, markerFactory: MarkerFactory<in LocationInlineQuery, Any> = ByUserInlineQueryMarkerFactory, scenarioReceiver: CustomBehaviourContextAndTypeReceiver<BC, Unit, LocationInlineQuery>): Job

Parameters

initialFilter

This filter will be called to remove unnecessary data BEFORE scenarioReceiver call

subcontextUpdatesFilter

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

markerFactory

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"

scenarioReceiver

Main callback which will be used to handle incoming data if initialFilter will pass that data