Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.17
•
• Add
•
•
Core:• Add
BotCommandScopeChat as new BotCommandScope (fix of #574•
BotCommandScope companion got several properties and functions for more useful scope creationGitHub
Release 0.38.17 · InsanusMokrassar/TelegramBotAPI
Core:
Add BotCommandScopeChat as new BotCommandScope (fix of #574)
BotCommandScope companion got several properties and functions for more useful scope creation
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 :)
GitHub
1.0.0 by InsanusMokrassar · Pull Request #564 · InsanusMokrassar/TelegramBotAPI
Type-safe library for work with Telegram Bot API. Contribute to InsanusMokrassar/TelegramBotAPI development by creating an account on GitHub.
Please, do not update
tgbotapi up to 0.38.18 - there is a bug in there and currently I am working on itForwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.19
•
• Hotfixes
•
•
• Now it is possible to define additional handlers in subcontexts of
•
BehaviourBuilder:• Hotfixes
•
BehaviourBuilder FSM:•
BehaviourContextWithFSMBuilder deprecated in favor to BehaviourContextWithFSM• Now it is possible to define additional handlers in subcontexts of
BehaviourBuilderWithFSMGitHub
Release 0.38.19 · InsanusMokrassar/TelegramBotAPI
BehaviourBuilder:
Hotfixes
BehaviourBuilder FSM:
BehaviourContextWithFSMBuilder deprecated in favor to BehaviourContextWithFSM
Now it is possible to define additional handlers in subcontexts of...
Hotfixes
BehaviourBuilder FSM:
BehaviourContextWithFSMBuilder deprecated in favor to BehaviourContextWithFSM
Now it is possible to define additional handlers in subcontexts of...
👍1
Several news:
• New version 0.38.21 with fixes and improvements
• Improve WebApp example: Now you may try inline buttons and reply markup buttons, use testServer for requests and look how to work with the results of WebApp via sendData or via sending data to server and making answer to the telegram system there
• New version 0.38.21 with fixes and improvements
• Improve WebApp example: Now you may try inline buttons and reply markup buttons, use testServer for requests and look how to work with the results of WebApp via sendData or via sending data to server and making answer to the telegram system there
GitHub
Release 0.38.21 · InsanusMokrassar/TelegramBotAPI
WebApps:
WebAppInitData#queryId now have correct js name of field
New function sendDataOrWorkWithQueryId
WebAppInitData#queryId now have correct js name of field
New function sendDataOrWorkWithQueryId
🔥3
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.23
•
• Add support of fallback triggers (fix of #560)
•
BehaviourHandler:• Add support of fallback triggers (fix of #560)
GitHub
Release 0.38.23 · InsanusMokrassar/TelegramBotAPI
BehaviourHandler:
Add support of fallback triggers (fix of #560)
Add support of fallback triggers (fix of #560)
👍3
Hello :) I wished to remind you, that today is the last chance to suggest your ideas to include them into 1.0.0 😏
GitHub
1.0.0 by InsanusMokrassar · Pull Request #564 · InsanusMokrassar/TelegramBotAPI
Type-safe library for work with Telegram Bot API. Contribute to InsanusMokrassar/TelegramBotAPI development by creating an account on GitHub.
🎉 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
•
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 TelegramMediaGitHub
Release 1.0.0 · InsanusMokrassar/TelegramBotAPI
All the tgbotapi.extensions.* packages have been removed
Versions:
Kotlin: 1.6.10 -> 1.6.21
Ktor: 1.6.8 -> 2.0.1
MicroUtils: 0.9.24 -> 0.10.2
Core:
Ktor package renamed. Migration: de...
Versions:
Kotlin: 1.6.10 -> 1.6.21
Ktor: 1.6.8 -> 2.0.1
MicroUtils: 0.9.24 -> 0.10.2
Core:
Ktor package renamed. Migration: de...
🎉7🔥3
How is your migration onto 1.0.0 (actually 1.1.0)?
Final Results
20%
Have migrated all actual projects
20%
Have migrated some actual projects
10%
Still on under 1.0.0 in actual projects, but plan to migrate
0%
Will not migrate onto 1.0.0
50%
Wa? 1.what?
Two small news:
• tgbotapi 1.1.1 is available for use and there I fixed checkWebAppLink method of TelegramAPIUrlsKeeper
• In examples of webapps now available example of web app data checking
• tgbotapi 1.1.1 is available for use and there I fixed checkWebAppLink method of TelegramAPIUrlsKeeper
• In examples of webapps now available example of web app data checking
GitHub
Release 1.1.1 · InsanusMokrassar/TelegramBotAPI
Versions:
MicroUtils.Crypto will not be provided with that library anymore. Instead, it is recommended to use Korlibs.Krypto. You still can add crypto from microutils using next groovy dependency:...
MicroUtils.Crypto will not be provided with that library anymore. Instead, it is recommended to use Korlibs.Krypto. You still can add crypto from microutils using next groovy dependency:...
👍1
• In version 1.1.2 I have added
• In 1.1.3 I've deprecated
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 redundantGitHub
Release 1.1.2 · InsanusMokrassar/TelegramBotAPI
Core:
Rename of TelegramAPIUrlsKeeper#checkWebAppLink -> TelegramAPIUrlsKeeper#checkWebAppData (fix of #591)
Behaviour Builder with FSM:
New typealias StateHandlingErrorHandler
BehaviourBuil...
Rename of TelegramAPIUrlsKeeper#checkWebAppLink -> TelegramAPIUrlsKeeper#checkWebAppData (fix of #591)
Behaviour Builder with FSM:
New typealias StateHandlingErrorHandler
BehaviourBuil...
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
I hope, it will help you to create more useful and clean code 😌
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
So, 2.0 is out and you may use new waiters API :) Besides, I have fixed behaviour of behaviour builder (😁), updated bookstack and examples (here migration onto 2.0)
GitHub
Release 2.0.0 · InsanusMokrassar/TelegramBotAPI
ALL PREVIOUS DEPRECATIONS HAVE BEEN REMOVED
Behaviour Builder:
Mappers have been removed from waiters extensions
Triggers extensions now will use filtering inside of context receiver instead of p...
Behaviour Builder:
Mappers have been removed from waiters extensions
Triggers extensions now will use filtering inside of context receiver instead of p...
Hello everybody :) on the soundcloud appeared my interview in russian about Kotlin Multiplatform, this library and several other topics :) Enjoy 🎉
SoundCloud
Hear the world’s sounds
Explore the largest community of artists, bands, podcasters and creators of music & audio
🔥1
Hello everybody :) small news: in 2.0.1 it becomes possitble to use any
UpdatesFilter in longPollingGitHub
Release 2.0.1 · InsanusMokrassar/TelegramBotAPI
Versions:
Ktor: 2.0.1 -> 2.0.2
MicroUtils: 0.10.5 -> 0.10.8
Utils:
TelegramBot#longPolling now accepts UpdatesFilter instead of FlowsUpdatesFilter
Ktor: 2.0.1 -> 2.0.2
MicroUtils: 0.10.5 -> 0.10.8
Utils:
TelegramBot#longPolling now accepts UpdatesFilter instead of FlowsUpdatesFilter
What whould you like to see in near time? (You may specify more info in comments)
Final Results
50%
Some additional docs
75%
Some additional tutorials/posts
38%
Some features
13%
Just keep it working, it is perfect
Kotlin Telegram Bot API Library (tgbotapi)
What whould you like to see in near time? (You may specify more info in comments)
Let's start :) How do you think, which tutorials/posts would be useful to see in near time?
Hello everybody :) today I and @akkihi have published the first version (
Fun fact: the name of the library is read by transcription [ˈkeɪsɪ] [lɒg]
0.0.1 😊) version of new library KSLog (kdocs). This is small and simple library for logging for JVM/JS/Android platforms. Potentially, this library will appear in our tgbotapi, and in that case your feedback will help to improve this library too :)Fun fact: the name of the library is read by transcription [ˈkeɪsɪ] [lɒg]
GitHub
GitHub - InsanusMokrassar/KSLog: Simple multiplatform logging in Kotlin
Simple multiplatform logging in Kotlin. Contribute to InsanusMokrassar/KSLog development by creating an account on GitHub.
👍2🥰1