Channel address:
Categories:
Apps
Language: English
Subscribers:
93
Description from channel
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
Ratings & Reviews
Reviews can be left only by registered users. All reviews are moderated by admins.
5 stars
0
4 stars
0
3 stars
0
2 stars
2
1 stars
0
The latest Messages 2
2021-11-06 16:18:35
Hello :) as you know, Telegram Bot API 5.4 has been introduced and becides I had updated FSM in my microutils libs. Due to these updates it was solved to:
• Make new major version
• Make breaking changes in FSM subproject
• Of course, implement telegram bot api 5.4
Due to changes in FSM, it is not recommended to start some project with that. I plan to release new version in one week (ideally, this monday), so, I hope that the delay will not be big :)
67 viewsedited 13:18
2021-10-24 11:34:25
Hello :) thanks to @djaler, we can meet 0.36.1 version with fixes in behaviour builder commands and new opportunity in entities builder - usage of separator and inheritage of it in subentities (like bold { })
130 views08:34
2021-10-22 14:07:22
For some explanation:
buildEntities variant:
buildEntities {
bold(
buildEntities { +"Some bold" + italic("and italic") }
)
+ "and regular"
}
Should print "
Some bold and italic and regular"
Second variant mostly about renaming buildEntities extension in the example to make it more obvious (it is not very predictive on first try that the second buildEntities will reuse its parent separator)
Of course, your solutions are welcome too
90 views11:07
2021-10-22 14:00:53
6 voters95 views11:00
2021-10-22 14:00:48
Hello :) currently @djaler is preparing improvement for Entities Builder. This improvement will add separator TextSource to EntitiesBuilder which will be automatically added between incoming text sources automatically. We faced with one important moment: we want to reuse separator in sub builders, BUT we are not sure how to make it good. There are several options we found:
65 views11:00
2021-10-18 17:43:24
New version 0.36.0 has been released and it contains a lot of important changes:
• As always,
all deprecations have been removed
• New packages for extensions now you may write tgbotapi.api instead tgboatpi.extensions.api and similarly for all other extensions. Old packages will be available until next major release
• New keyboard DSL: say goodbye to ReplyKeyboardMarkup(matrix { row { ... } }) and hello to replyKeyboard { row { simpleButton("") } }
• New integration of FSM into Behaviour Builder in new package tgbotapi.behaviour_builder.fsm: in this realization taken attention for more closed work with FSM inside of telegram bots
• New type WithUser. Now FromUser is extending WithUser and any tgbotapi type with user implements type WithUser. It is imortant, that constructors of classes-implementors of FromUser has changed their incoming parameters names from user to from due to renames inside of FromUser, but you still may use user field for FromUser objects
Besides, I recommend you to read a small note about flows and changes of mechanisms inside of behaviour builder and full changelog if you want to know all news
67 viewsedited 14:43
2021-10-18 13:43:24
A little update is on the way :)
54 views10:43
2021-10-17 07:24:06
FromUser improvements · Issue #484 · InsanusMokrassar/TelegramBotAPI
https://github.com/InsanusMokrassar/TelegramBotAPI/issues/484
56 views04:24
2021-10-14 06:51:26
8 voters63 views03:51
2021-10-05 15:10:29
10 voters72 views12:10