Kotlin Telegram Bot API Library (tgbotapi)
160 subscribers
17 photos
1 video
1 file
276 links
https://github.com/InsanusMokrassar/ktgbotapi

Channel with updates from Kotlin Multiplatform TelegramBotAPI library

DM: @InsanusMokrassar
Forum: @ktgbotapi_forum
Projects Releases: @inmodev
Support me: https://t.me/inmodev/431
Download Telegram
Somewhere in the middle of 1.0.0 update...
2👍2🔥2
This update is just cherry-pick release from 1.0.0 with support of Telegram Bot API 6.0. Potentially this update may contains breaking changes, but I wished to bring you new api version without long waiting for the 1.0.0 release
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.14

This update contains including of Telegram Bot API 6.0

Core:
• Constructor of UnknownInlineKeyboardButton is not internal and can be created with any json
WebApps:
• Created 🎉
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.15

Common:
Version:
MicroUtils: 0.9.20 -> 0.9.24
Core:
• Fixes in MessageContent#serializationModule
BehaviourBuilder:
• Add triggers for DataCallbackQuery and subtypes with regex checking of data
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.16

Core:
TelegramAPIUrlsKeeper now have two new things: properties webAppDataSecretKey and fun checkWebAppLink
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.17

Core:
• Add BotCommandScopeChat as new BotCommandScope (fix of #574
BotCommandScope companion got several properties and functions for more useful scope creation
Hello everybody :) it looks like work with refactoring of classpathes in 1.0.0 has been completed and currently I am thinking about the things we could add in that release. In case you wished to suggest something, it seems to be the best time for that :)
Please, do not update tgbotapi up to 0.38.18 - there is a bug in there and currently I am working on it
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.19

BehaviourBuilder:
• Hotfixes
BehaviourBuilder FSM:
BehaviourContextWithFSMBuilder deprecated in favor to BehaviourContextWithFSM
• Now it is possible to define additional handlers in subcontexts of BehaviourBuilderWithFSM
👍1
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.23

BehaviourHandler:
• Add support of fallback triggers (fix of #560)
👍3
🎉 1.0.0 has been released 🎉 In examples repository you may find PR with migration onto 1.0.0

Several notes:

• A lot of renames in packages and replaces of objects. Most of them should be backward compatible with 0.38.23
• A lot of rewritings in interfaces related to the sealing of interfaces
• Complex of dependencies updates: Kotlin 1.6.21, Ktor 2.0.1, etc.
• Fixes and improvements in BehaviourBuilder and BehaviourBuilderWithFSM
StorageFile has been deprecated and now it is enough to use MultipartFile everywhere
InputMedia (and all subsequent functions) has been renamed to TelegramMedia
🎉7🔥3
• In version 1.1.2 I have added StateHandlingErrorHandler and functionality in BehaviourContextWithFSM to handle states handling errors
• In 1.1.3 I've deprecated StateHandlingErrorHandler cause I've added the same functionality in default states machines in microutils and typealias in tgbotapi is redundant
Currently, in all wait* extensions in BehaviourBuilder there is "mapper" parameter, which allow you to change the data before the returning. I want to remove this parameter due to its useless (imho) and I wished to ask - do you use mapper parameter?
Final Results
0%
Yes
20%
No
80%
Wa... What parameter?
Something big (or not) is coming...
🤔3
Hello everybody :)

In the future 2.0.0 release I finally realized how waiters of BehaviourBuilder should look like: they will return the Flow with required data and you will be able to filter, map, take as much as required and do with that flow anything you want to. It is breaking change: you will not be able to use parameter count (you will use take(count) instead), filter or mapper - all they will be replaced with standard flows functionality.

I hope, it will help you to create more useful and clean code 😌
🔥3