Several days ago I have added new sample parts in examples for webapps. Besides, I have published 3.1.1 with webapps bot api 6.2 support
GitHub
TelegramBotAPI-examples/main.kt at a8c5d403c6a270bae9efdedca09a12d47f80ecf9 · InsanusMokrassar/TelegramBotAPI-examples
This repository contains several examples of simple bots which are using TelegramBotAPI - TelegramBotAPI-examples/main.kt at a8c5d403c6a270bae9efdedca09a12d47f80ecf9 · InsanusMokrassar/TelegramBotA...
👍2
Hi :) I am preparing new update and there is a chance to change behaviour of main `execute` - I plan to wrap all the exceptions happen inside to additional exception. So, the main question:
Do you use handling of some specific exceptions thrown from bot?
Do you use handling of some specific exceptions thrown from bot?
Anonymous Poll
50%
Yes
25%
No
25%
Just use safely/runCatchingSafely/etc.
Sometimes I am thinking about some coding-streams. On these strems we could talk about the future of this library, kotlin, bots and (I think) something else. Would you be interest in this?
Anonymous Poll
61%
Yes
6%
No
33%
Maybe yes or maybe not, I forgot
Version 3.1.2 has been transformed to 3.2.0 and published 🎉 whats new:
• All
• New extensions for behaviour builder
• IMPORTANT CHANGE:(aka ) will throw only
• All
allowedUpdates will be setup to ALL_UPDATES_LIST by default• New extensions for behaviour builder
waitDeepLinks/onDeepLink + improved support of deep links creation• IMPORTANT CHANGE:
execute method of TelegramBot RequestsExecutorBotExceptions since this update. Please, check exceptions catching in your projects and fix themGitHub
Release 3.2.0 · InsanusMokrassar/TelegramBotAPI
Since this update, RequestsExecutor#execute may throw only BotException. In case you wish to handle some exceptions from execute you must catch BotException and handle its cause
Versions:
Seriali...
Versions:
Seriali...
Hello everybody :) You may find all the versions of my libraries (including tgbotapi) on my github page. I hope this will be useful for those who is using more than one :)
GitHub
InsanusMokrassar/README.md at master · InsanusMokrassar/InsanusMokrassar
Contribute to InsanusMokrassar/InsanusMokrassar development by creating an account on GitHub.
🤩4
Version 3.2.3 is available. Short highlight about changes since 3.2.0:
• Dependencies updates
• Fixes in
• New
• Dependencies updates
• Fixes in
DeleteMyCommands• New
reply extensions with chatId and messageIdGitHub
Release 3.2.3 · InsanusMokrassar/TelegramBotAPI
Core:
Fixes in DeleteMyCommands
Fixes in DeleteMyCommands
👍4
I have faced with the new mechanism of stacktrace recovery in coroutines. As I understand, one of the part of this recovery process is to copy old exception into the same new one with the old passing as cause of new.
In two words, we have started to get CommonBotException in CommonBotExceptions 😐
I have fixed this problem in the 3.2.5 and currently preparing 3.2.6 with fix of
In two words, we have started to get CommonBotException in CommonBotExceptions 😐
I have fixed this problem in the 3.2.5 and currently preparing 3.2.6 with fix of
ChatMember serialization and plan to add requests builders DSL as shown in #657 issue. You are welcome with any suggestions in comments or in my DM about some features/fixes/improvements for lib :)GitHub
Release 3.2.5 · InsanusMokrassar/TelegramBotAPI
Common:
Improve support of new exceptions recovering mechanism
Improve support of new exceptions recovering mechanism
Some time ago Telegram have published their introducing tutorial based on Java, Maven and rubenlagus/TelegramBots. One of our community members have prepared an analogue with our stack: Kotlin, Gradle and InsanusMokrassar/TelegramBotAPI:
https://madhead.me/posts/from-botfather-to-hello-world
https://madhead.me/posts/from-botfather-to-hello-world
❤5
In new version (3.3.1) will be added new extension "hasNoCommands". Should we use it by default in on content triggers (like onContentMessage)?
Anonymous Poll
57%
Yes
7%
No
36%
Whareve
3.3.1 released 🎉 In two words:
• Dependencies update
• Fixes in multipart requests (thanks to @ithersta report)
• New extensions
• Dependencies update
• Fixes in multipart requests (thanks to @ithersta report)
• New extensions
CommonMessage#hasCommands/CommonMessage#hasNoCommands (thanks to @m_a_d_h_e_a_d contribution)GitHub
Release 3.3.1 · InsanusMokrassar/TelegramBotAPI
Versions:
Ktor: 2.1.2 -> 2.1.3
Klock: 3.2.0 -> 3.3.1
MicroUtils: 0.13.1 -> 0.13.2
Utils:
New extensions on CommonMessage: hasCommands and hasNoCommands. Useful for the initialFilter pa...
Ktor: 2.1.2 -> 2.1.3
Klock: 3.2.0 -> 3.3.1
MicroUtils: 0.13.1 -> 0.13.2
Utils:
New extensions on CommonMessage: hasCommands and hasNoCommands. Useful for the initialFilter pa...
🎉5
In the Bot API 6.3 new term "forum" has been introduced. Forum is the group chat (supergroup chats, I suppose) with the topics enabled. Currently I am thinking about how to implement it and there are two ways:
• Add new type of chats extending Group/Supergroup
• Add the flag in Group/Supergroup as a sign of forum chat
• Add new type of chats extending Group/Supergroup
• Add the flag in Group/Supergroup as a sign of forum chat
I plan to rework media groups as content of common messages instead of different types of messages. It is very complex change in API and brings a lot of breaking changes. What would be better in your opinion?
Final Results
53%
Rework everything with Bot API 6.3 - there will be breaking changes anyway
33%
Rework everything in the next major release (maybe right after this release)
13%
Don't touch holy media groups!