com.bot4s.telegram.api.declarative
Callbacks
Related Doc:
package declarative
Send a response for a callback query.
Send a response for a callback query. Callback queries must ack-ed e.g. ackCallback(), even if no response is sent.
Text of the notification. If not specified, nothing will be shown to the user
If true, an alert will be shown by the client instead of a notification at the top of the chat screen. Defaults to false.
URL that will be opened by the user's client. If you have created a Game and accepted the conditions via @Botfather, specify the URL that opens your game - note that this will only work if the query comes from a callback_game button.
The maximum amount of time in seconds that the result of the callback query may be cached client-side. Telegram apps will support caching starting in version 3.14. Defaults to 0.
A future containing the result of the AnswerCallbackQuery request.
Allowed updates.
Allowed updates. See UpdateType.Filters. By default all updates are allowed.
Allowed updates. None indicates no-filtering (all updates allowed).
import UpdateType.Filters._ override def allowedUpdates: Option[Seq[UpdateType]] = Some(MessageUpdates ++ InlineUpdates)
Executes 'action' for every incoming callback query.
Filter callbacks based on a tag (to avoid collision).
Filter callbacks based on a tag (to avoid collision). The tag is stripped from the CallbackQuery object when passed to the handler.
Tag
Handler to process the filtered callback query.
Helper to tag 'callbackData' in inline markups.
Helper to tag 'callbackData' in inline markups. Usage:
def tag = prefixTag("MY_TAG") _ ... callbackData = tag("some data")
Dispatch updates to specialized handlers.
Dispatch updates to specialized handlers. Incoming update can be a message, edited message, channel post, edited channel post, inline query, inline query results (sample), callback query, shipping or pre-checkout events.
Incoming update.
Declarative interface for callbacks; allows filtering callback-query events by tag.