I am preparing new release and wished to know your opinion about class casts feature namings (extensions like asBot/requireBot/onBot) and specially about chaning of that naming to if*/*OrNull/*OrThrow (like ifBot, botOrNull/botOrThrow)
Final Results
0%
Do not use
71%
New variant with if/OrNull/OrThrow is better
29%
Use and naming is ok
• New version 2.2.0 with fixes and improvements has been published
• Also new version of plagubot has been published too :)
• I am working on welcome tutorial plugin and currently the article is not ready, but you may try this plugin in its branch!
• Also new version of plagubot has been published too :)
• I am working on welcome tutorial plugin and currently the article is not ready, but you may try this plugin in its branch!
GitHub
Release 2.2.0 · InsanusMokrassar/TelegramBotAPI
Core:
For CopyMessage order of parameters has been changed
ReplyForce defaults changes:
All old companion properties (like ReplyForce.ReplyForceSelective) have been renamed:
ReplyForceSelective ...
For CopyMessage order of parameters has been changed
ReplyForce defaults changes:
All old companion properties (like ReplyForce.ReplyForceSelective) have been renamed:
ReplyForceSelective ...
Do you use microutils outside of tgbotapi?
Anonymous Poll
31%
Yes
54%
No
15%
Do not use even with tgbotapi
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 2.2.1
•
•
•
•
• New
•
• New extensions for all types of messages
•
Versions:•
Coroutines: 1.6.3 -> 1.6.4•
MicroUtils: 0.11.12 -> 0.11.13•
Core:• New
typealiases for CommonMessage with all supported content types, more info: PR•
Utils:• New extensions for all types of messages
•.withContentOrNull and •.withContentOrThrow as analogies to the same ones from class castsGitHub
Release 2.2.1 · InsanusMokrassar/TelegramBotAPI
Versions:
Coroutines: 1.6.3 -> 1.6.4
MicroUtils: 0.11.12 -> 0.11.13
Core:
New typealiases for CommonMessage with all supported content types, more info: PR
Utils:
New extensions for al...
Coroutines: 1.6.3 -> 1.6.4
MicroUtils: 0.11.12 -> 0.11.13
Core:
New typealiases for CommonMessage with all supported content types, more info: PR
Utils:
New extensions for al...
Forwarded from inmo.dev
GitHub
Release 1.3.1 · InsanusMokrassar/PlaguBot
Versions:
tgbotapi: 2.2.1
microutils: 0.11.13
tgbotapi: 2.2.1
microutils: 0.11.13
Hello everybody :) I am preparing tgbotapi 3.0.0 with kotlin 1.7.10. You may suggest some additions/changes/features in comments to discuss including those in this release.
UPD: 3.0.0 Milestone
UPD: 3.0.0 Milestone
GitHub
3.0.0 by InsanusMokrassar · Pull Request #634 · InsanusMokrassar/TelegramBotAPI
Type-safe library for work with Telegram Bot API. Contribute to InsanusMokrassar/TelegramBotAPI development by creating an account on GitHub.
👍4
Kotlin Telegram Bot API Library (tgbotapi)
Hello everybody :) I am preparing tgbotapi 3.0.0 with kotlin 1.7.10. You may suggest some additions/changes/features in comments to discuss including those in this release. UPD: 3.0.0 Milestone
I have tested this update and getting ready for release. Anyway, it is still good time for you to suggest new things in project 😏
So, 3.0.2 has been published. I have set the main point in this release is to update kotlin and related dependencies up to 1.7.10 and I didn't expect that in this version will be:
• Several important renames (for example,
• New API for live location streaming via coroutines flows
• Changes in structure of
Besides, in that update I have started to use KSP for generating of new classcasts. In case I missed some of the extensions you may write to me or in the chat and I will try hard to include them in next release.
Versions 3.0.0 and 3.0.1 have been published with errors and contain the same changes, but require redundant magic in dependencies
• Several important renames (for example,
ReplyMarkup -> WithReplyMarkup)• New API for live location streaming via coroutines flows
• Changes in structure of
ForwardInfoBesides, in that update I have started to use KSP for generating of new classcasts. In case I missed some of the extensions you may write to me or in the chat and I will try hard to include them in next release.
GitHub
Release 3.0.2 · InsanusMokrassar/TelegramBotAPI
ALL OLD DEPRECATIONS HAVE BEEN REMOVED
copyMessage HAVE CHANGED THEIR SIGNATURE BY SWAPPING FROM AND TO CHAT IDS
Versions:
Kotlin: 1.6.21 -> 1.7.10
Serialization: 1.3.3 -> 1.4.0-RC
Korlibs:...
copyMessage HAVE CHANGED THEIR SIGNATURE BY SWAPPING FROM AND TO CHAT IDS
Versions:
Kotlin: 1.6.21 -> 1.7.10
Serialization: 1.3.3 -> 1.4.0-RC
Korlibs:...
What version do you use?
Anonymous Poll
17%
0.*
8%
1.*
17%
2.*
58%
3.*
8%
Other (O.o), will write in comments
Version 3.1.0 is out and you may start to work with new stickers. Unfortunatelly, there are several issues related to this functionality:
• Bots currently can't create custom emoji's sticker sets
• Bots currently can't send custom emojis. Technically, you may include custom emojis in your text, but they will appear as regular text and no information about emoji will exists in message
Besides, I have fully reworked hierarchy of stickers and sticker sets. I hope that it will not break anything in your code, but I strongly recommend you to recompile your projects if you want to update this library dependency
• Bots currently can't create custom emoji's sticker sets
• Bots currently can't send custom emojis. Technically, you may include custom emojis in your text, but they will appear as regular text and no information about emoji will exists in message
Besides, I have fully reworked hierarchy of stickers and sticker sets. I hope that it will not break anything in your code, but I strongly recommend you to recompile your projects if you want to update this library dependency
GitHub
Release 3.1.0 · InsanusMokrassar/TelegramBotAPI
This update contains including of Bot API 6.2
Versions:
Ktor: 2.0.3 -> 2.1.0
MicroUtils: 0.12.0 -> 0.12.1
Core:
Add support of custom emojis
Add support of sticker_type
Versions:
Ktor: 2.0.3 -> 2.1.0
MicroUtils: 0.12.0 -> 0.12.1
Core:
Add support of custom emojis
Add support of sticker_type
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