In case this library will be updated up to kotlin 1.6, will you be ready to migrate too?
Anonymous Poll
100%
Yes
0%
No
👍3
Kotlin Telegram Bot API Library (tgbotapi) via @TGStat_Bot
Photo
Our humble statistic 😊 Thank you for your critics, support and help :)
0.38.0 version of update has been released :) here mainly update up to Kotlin 1.6, update up to Telegram Bot API 5.6 and several fixes
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.0
This update contains Telegram Bot API 5.6 implementation
This update contains migration onto Kotlin 1.6
This update has changed constructors of all
•
•
•
•
•
•
•
•
•
• Add
• Add support of
• ALL IMPLEMENTERS OF
•
•
•
•
•
•
•
•
•
This update contains Telegram Bot API 5.6 implementation
This update contains migration onto Kotlin 1.6
This update has changed constructors of all
CommonMessage implementations•
Common:•
Version:•
Kotlin: 1.5.31 -> 1.6.10•
Coroutines: 1.5.2 -> 1.6.0•
Serialization: 1.3.1 -> 1.3.2•
Klock: 2.4.8 -> 2.4.10•
Ktor: 1.6.5 -> 1.6.7•
MicroUtils: 0.8.7 -> 0.9.0•
Core:• Add
SpoilerTextSource (as part of Telegram Bot API 5.6 update)• Add support of
protect_content as a field protectContent in all send message requests and parameter in all functions related to that requests (as part of Telegram Bot API 5.6 update)• ALL IMPLEMENTERS OF
CommonMessage HAS CHANGED THEIR CONSTRUCTOR: NOW THEY GET hasProtectedContent instead of forwardable (inversed) field•
ChannelContentMessageImpl•
ChannelMediaGroupMessage•
CommonMediaGroupMessage•
GroupContentMessage implementers•
ConnectedFromChannelGroupContentMessageImpl•
UnconnectedFromChannelGroupContentMessageImpl•
AnonymousGroupContentMessageImpl•
CommonGroupContentMessageImpl•
PrivateContentMessageImplGitHub
Release 0.38.0 · InsanusMokrassar/TelegramBotAPI
This update contains Telegram Bot API 5.6 implementation
This update contains migration onto Kotlin 1.6
This update has changed constructors of all CommonMessage implementations
Common:
Version:
...
This update contains migration onto Kotlin 1.6
This update has changed constructors of all CommonMessage implementations
Common:
Version:
...
👍2
0.38.1 PR is in work and I hope today I will release this version. Currently it is still in progress and you may offer some features to include in this update ☺️
GitHub
0.38.1 by InsanusMokrassar · Pull Request #524 · InsanusMokrassar/TelegramBotAPI
Type-safe library for work with Telegram Bot API. Contribute to InsanusMokrassar/TelegramBotAPI development by creating an account on GitHub.
Kotlin Telegram Bot API Library (tgbotapi)
0.38.1 PR is in work and I hope today I will release this version. Currently it is still in progress and you may offer some features to include in this update ☺️
Version 0.38.1 is available for including in your projects :) here:
• Realization of #511 issue
• Several small fixes, types clarifications and class casts addings
• Realization of #511 issue
• Several small fixes, types clarifications and class casts addings
GitHub
Release 0.38.1 · InsanusMokrassar/TelegramBotAPI
Core:
MessageCallbackQuery (and all implementers as well) has changed the type of message: now it is ContentMessage<MessageContent> instead of Message
New type ForwardFromPublicChatInfo as e...
MessageCallbackQuery (and all implementers as well) has changed the type of message: now it is ContentMessage<MessageContent> instead of Message
New type ForwardFromPublicChatInfo as e...
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.2
•
•
•
•
• New extensions
•
Common:•
Version:•
MicroUtils: 0.9.0 -> 0.9.1•
API• New extensions
TelegramBot#copyMessages for media groupsGitHub
Release 0.38.2 · InsanusMokrassar/TelegramBotAPI
Common:
Version:
MicroUtils: 0.9.0 -> 0.9.1
API
New extensions TelegramBot#copyMessages for media groups
Version:
MicroUtils: 0.9.0 -> 0.9.1
API
New extensions TelegramBot#copyMessages for media groups
❤1
Hello :) in 0.38.2 I wished to add media groups sending methods with content lists, but due to the signature clash I can't add methods with names like
How do you think, which names in that case would be better to choose for media groups sending by content? Add prefix or postfix like
sendMediaGroup due to their existance with input media lists.How do you think, which names in that case would be better to choose for media groups sending by content? Add prefix or postfix like
sendContentMediaGroup? Or something else? I would be glad to see your opinion :)Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.3
•
•
•
•
•
•
• New extensions
•
Common:•
Version:•
MicroUtils: 0.9.1 -> 0.9.2•
Klock: 2.4.10 -> 2.4.12•
UUID: 0.3.1 -> 0.4.0•
API• New extensions
TelegramBot#send• for media groups with contentsGitHub
Release 0.38.3 · InsanusMokrassar/TelegramBotAPI
Common:
Version:
MicroUtils: 0.9.1 -> 0.9.2
Klock: 2.4.10 -> 2.4.12
UUID: 0.3.1 -> 0.4.0
API
New extensions TelegramBot#send* for media groups with contents
Version:
MicroUtils: 0.9.1 -> 0.9.2
Klock: 2.4.10 -> 2.4.12
UUID: 0.3.1 -> 0.4.0
API
New extensions TelegramBot#send* for media groups with contents
Hello everybody, long time no see :) I've started 0.38.4 and you are welcome with suggestions for this update :)
GitHub
0.38.4 by InsanusMokrassar · Pull Request #530 · InsanusMokrassar/TelegramBotAPI
Type-safe library for work with Telegram Bot API. Contribute to InsanusMokrassar/TelegramBotAPI development by creating an account on GitHub.
🔥1
Kotlin Telegram Bot API Library (tgbotapi)
Hello everybody, long time no see :) I've started 0.38.4 and you are welcome with suggestions for this update :)
core.telegram.org
Bot API changelog
The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram. To learn how to create…
👍4
Release 0.38.4 is available in maven central. Here:
• Fix of #529
• Realization of Telegram Bot API 5.7, including:
• Separation of Sticker to SimpleSticer, AnimatedSticker and VideoSticker
• Fix of #529
• Realization of Telegram Bot API 5.7, including:
• Separation of Sticker to SimpleSticer, AnimatedSticker and VideoSticker
GitHub
Release 0.38.4 · InsanusMokrassar/TelegramBotAPI
This update contains including of Telegram Bot API 5.7
Core:
Support of new fields Sticker
Support of new fields StickerSet
Support of new fields in creating of sticker set and sticker
Utils:
...
Core:
Support of new fields Sticker
Support of new fields StickerSet
Support of new fields in creating of sticker set and sticker
Utils:
...
❤2🔥1
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.6
•
•
•
•
•
• New member of
•
Common:•
Version:•
MicroUtils: 0.9.6 -> 0.9.9•
Klock: 2.4.13 -> 2.5.2•
Core:• New member of
MentionTextSource - usernameGitHub
Release 0.38.6 · InsanusMokrassar/ktgbotapi
Common:
Version:
MicroUtils: 0.9.6 -> 0.9.9
Klock: 2.4.13 -> 2.5.2
Core:
New member of MentionTextSource - username
Version:
MicroUtils: 0.9.6 -> 0.9.9
Klock: 2.4.13 -> 2.5.2
Core:
New member of MentionTextSource - username
Hello everybody :) I have started 0.38.7 version and currently thinking what to add there also. You are always welcome with your suggestions for including in near release
GitHub
0.38.7 by InsanusMokrassar · Pull Request #540 · InsanusMokrassar/TelegramBotAPI
Type-safe library for work with Telegram Bot API. Contribute to InsanusMokrassar/TelegramBotAPI development by creating an account on GitHub.
👍1
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.7
•
•
•
•
•
•
• New function
•
Common:•
Version:•
MicroUtils: 0.9.9 -> 0.9.12•
Klock: 2.5.2 -> 2.6.2•
Core:•
SimplePollOption#votes now is 0 by default• New function
PollOption.Companion#simpleGitHub
Release 0.38.7 · InsanusMokrassar/ktgbotapi
Common:
Version:
MicroUtils: 0.9.9 -> 0.9.12
Klock: 2.5.2 -> 2.6.2
Core:
SimplePollOption#votes now is 0 by default
New function PollOption.Companion#simple
Version:
MicroUtils: 0.9.9 -> 0.9.12
Klock: 2.5.2 -> 2.6.2
Core:
SimplePollOption#votes now is 0 by default
New function PollOption.Companion#simple
👍1
Hello everybody. I wished to ask you about some painful/hard/incorrect places in library you would like to see fixed. What you would like to see in documentation asap? Or maybe you want to have some DSL/extension you are using in different projects. You are welcome in comments or in direct messages