.. | ||
src/commonMain/kotlin/dev/inmo/tgbotapi/extensions/api | ||
build.gradle | ||
maven.publish.gradle | ||
mpp_publish_template.kpsb | ||
publish.gradle | ||
README.md |
TelegramBotAPI extensions
What is it?
It is wrapper library for TelegramBotAPI-core. Here you can find extensions for
RequestsExecutor
, which are more look like Telegram Bot API requests and in the same time have more obvious signatures
to help understand some restrictions in Telegram system.
Compatibility
This library always compatible with original TelegramBotAPI-core
library version
How to implement library?
Common ways to implement this library are presented here. In some cases it will require additional steps
like inserting of additional libraries (like kotlin stdlib
). In the examples will be used variable
telegrambotapi-extensions-api.version
, which must be set up by developer. Available versions are presented on
bintray, next version is last published:
Maven
Dependency config presented here:
<dependency>
<groupId>dev.inmo</groupId>
<artifactId>TelegramBotAPI-extensions-api</artifactId>
<version>${telegrambotapi-extensions-api.version}</version>
</dependency>
Gradle
To use last versions you will need to add one line in repositories block of your build.gradle
:
jcenter()
or mavenCentral()
And add next line to your dependencies block:
implementation "dev.inmo:TelegramBotAPI-extensions-api:$telegrambotapi_extensions_api_version"
or for old gradle:
compile "dev.inmo:TelegramBotAPI-extensions-api:$telegrambotapi_extensions_api_version"
Example of usage and comparison with TelegramBotAPI
Here presented review table for comparison of api from original TelegramBotAPI and extensions-api library. First of all, this library allow to create bot instance in a new way:
val bot = telegramBot("IT IS YOUR TOKEN")
There are a lot of signature for this. For example, you can create bot with next code:
val bot = telegramBot("IT IS YOUR TOKEN") {
proxy = ProxyBuilder.socks("127.0.0.1", 1080)
}
In all examples supposed that you have created bot.
TelegramBotAPI-core | TelegramBotAPI-extensions-api |
---|---|
bot.execute(GetMe) | bot.getMe() |
bot.execute(SendTextMessage(someChatId, text)) | bot.sendTextMessage(chat, text) |
Updates
Currently, these paragraphs almost outdated due to the fact that extensions for listening of updates and webhooks were
replaced into TelegramBotAPI-extensions-utils
. But, most part of information below is correct with small fixes and
adding of TelegramBotAPI-extensions-utils
dependency.
Usually, it is more comfortable to use filter object to get separated types of updates:
val filter = FlowsUpdatesFilter(100)
In this case you will be able:
- Separate types of incoming updates (even media groups)
- Simplify launch of getting updates:
bot.startGettingOfUpdates(
filter,
scope = CoroutineScope(Dispatchers.Default)
)
- Use
filter
flows to comfortable filter, map and do other operations with the whole getting updates process:
filter.messageFlow.mapNotNull {
it.data as? ContentMessage<*>
}.onEach {
println(it)
}.launchIn(
CoroutineScope(Dispatchers.Default)
)
Alternative way
There is an alternative way to get updates. In fact it is almost the same, but could be more useful for some cases:
val filter = bot.startGettingOfUpdates(
scope = CoroutineScope(Dispatchers.Default)
) { // Here as reveiver will be FlowsUpdatesFilter
messageFlow.mapNotNull {
it.data as? ContentMessage<*>
}.onEach {
println(it)
}.launchIn(
CoroutineScope(Dispatchers.Default)
)
}