0.34.1 has been released and it is strongly recommended to update it in your project in case you are using 0.34.0
GitHub
Release 0.34.1 Β· InsanusMokrassar/TelegramBotAPI
Common:
Version:
ktor: 1.5.3 -> 1.5.4
MicroUtils: 0.4.35 -> 0.4.36
Core
Fix in creating of text sources list
Version:
ktor: 1.5.3 -> 1.5.4
MicroUtils: 0.4.35 -> 0.4.36
Core
Fix in creating of text sources list
Hello everybody:) I am currently thinking about some FSM (or just state machine) realization for bots based on our library, but I have no good ideas about implementation of it. For now the most important criteria is to create usefull and easy-to-use part with, maybe, some DSL.
You are welcome with your suggestionsπ
You are welcome with your suggestionsπ
Hello :) New version of kotlin, 1.5.10, has been release and have fixed several critical issues in work with inline value classes. So, I plan to start new version with migration onto this version. There are several questions which I will ask you in next poll:) I'd be glad to see your opinion
GitHub
Release Kotlin 1.5.10 Β· JetBrains/kotlin
How to update to a new release
Changelog
Compiler
Fixes
KT-41078 Incorrect type substitution in contracts with type parameters
KT-44770 JVM / IR: "IllegalArgumentException: Unrecognized Type:...
Changelog
Compiler
Fixes
KT-41078 Incorrect type substitution in contracts with type parameters
KT-44770 JVM / IR: "IllegalArgumentException: Unrecognized Type:...
What to include in next version? (BC - BreakingChanges)
Anonymous Poll
100%
Value classes for identifiers (BC)
100%
Using of sealed interfaces on the things like CallbackQuery (Half BC)
PR has been created and I (I suppose) have fixed build and issues related to included changes. Several highlights:
β’ Rewriting of internal sealed classes as sealed interfaces
β’ I have replaced simple interfaces by sealed interface where it was possible and replace several interfaces from the places like
β’ JS Legacy will not be supported since this update ( π )
Currently it is required to check everything on TelegramBotAPI-examples and my internal tests. After this I plan to rewrite different typealiases to value classes where it is posible.
β’ Rewriting of internal sealed classes as sealed interfaces
β’ I have replaced simple interfaces by sealed interface where it was possible and replace several interfaces from the places like
CommonAbstracts package to the packages according to these abstractions implementors/extendersβ’ JS Legacy will not be supported since this update ( π )
Currently it is required to check everything on TelegramBotAPI-examples and my internal tests. After this I plan to rewrite different typealiases to value classes where it is posible.
GitHub
0.35.0 by InsanusMokrassar Β· Pull Request #395 Β· InsanusMokrassar/TelegramBotAPI
That happened π Version 0.35.0 is available for using in your projects :) in two words:
β Contains breaking changes
π¦ Dependencies updates
π kotlin 1.5.10
π EntitiesBuilder got DSL part based on callbacks
π Most project use sealed interfaces
π Deprecations have been removed
β Contains breaking changes
π¦ Dependencies updates
π kotlin 1.5.10
π EntitiesBuilder got DSL part based on callbacks
π Most project use sealed interfaces
π Deprecations have been removed
GitHub
Release 0.35.0 Β· InsanusMokrassar/TelegramBotAPI
ALL PREVIOUS DEPRECATIONS HAVE BEEN REMOVED
JS PART NOW USE IR COMPILER ONLY
Common:
Version:
Kotlin: 1.4.72 -> 1.5.10
MicroUtils: 0.4.36 -> 0.5.6
Coroutines: 1.4.3 -> 1.5.0
Serializati...
JS PART NOW USE IR COMPILER ONLY
Common:
Version:
Kotlin: 1.4.72 -> 1.5.10
MicroUtils: 0.4.36 -> 0.5.6
Coroutines: 1.4.3 -> 1.5.0
Serializati...
Hello :) as usual, I am thinking about some features we may add to our library:) do you have some ideas? Maybe, there is something you want to see in this library? You are welcome in comments with your suggestions π
Hi again :) I've started creating of FSM which will be usefull with tgbotapi (and not only :) ). Here you will find some probable target api example of this FSM. Currently there are a few things left until this tool will be ready for preview releae:
β’ Add exposed and android realizations of StateManager (or some factory functions)
β’ Add basic states in tgbotapi.libraries project
β’ Add some usefull variant of FSM initializing in context of tgbotapi
Stay tuned, I hope, release of this tool will be soon :)
β’ Add exposed and android realizations of StateManager (or some factory functions)
β’ Add basic states in tgbotapi.libraries project
β’ Add some usefull variant of FSM initializing in context of tgbotapi
Stay tuned, I hope, release of this tool will be soon :)
GitHub
0.5.13 by InsanusMokrassar Β· Pull Request #77 Β· InsanusMokrassar/MicroUtils
Hello:) As you know, currently ib developing FSM which will be used in tgbotapi :) Which functionality of FSM is the most useful for you? Why? I will use your answers in future release, thank youβΊοΈ
GitHub
0.5.13 by InsanusMokrassar Β· Pull Request #77 Β· InsanusMokrassar/MicroUtils
New Bot API 5.3 has been included in near new version. Currently for this version left several things:
* Replace in triggers of behaviour builder parameter performInParallel by marker factory from micro_utils project
* Run already created tests and example bots
* Check new version
I hope, that tomorrow we will see new version in release and start use new functionality in our bots π
* Replace in triggers of behaviour builder parameter performInParallel by marker factory from micro_utils project
* Run already created tests and example bots
* Check new version
I hope, that tomorrow we will see new version in release and start use new functionality in our bots π
core.telegram.org
Bot API changelog
The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram. To learn how to createβ¦
Update 0.35.1 is almost here and it is nice time to offer some improvements to include them in this release π I plan to release this version this evening, so you are welcome π
GitHub
0.35.1 by InsanusMokrassar Β· Pull Request #421 Β· InsanusMokrassar/TelegramBotAPI
0.35.1 has been started as small update and now we are here :)
Update 0.35.1 has been merged and now on its way to maven repo and you may read full changelog of this update. In two words:
β’ π Ofcourse, full actualization up to Telegram Bot API 5.3
β’ π New casts type
β’ π
β’ π All message content now is serializable by default
β’ π Several interfaces/classes became
β’ β
β’ π Factories
β’ π Entities builder got improvements
β’ β
β’ π Ofcourse, full actualization up to Telegram Bot API 5.3
β’ π New casts type
when* - now you may call code like message.whenContentMessage { it.content }β’ π
make*String extensions (as a replacement for old makeString and internal functions for html/markdown)β’ π All message content now is serializable by default
β’ π Several interfaces/classes became
sealedβ’ β
on* extensions of BehaviourBuilder will works in parallelβ’ π Factories
telegramBotWithBehaviourβ’ π Entities builder got improvements
β’ β
reply extension have been replaced to avoid import conflictsGitHub
0.35.1 by InsanusMokrassar Β· Pull Request #421 Β· InsanusMokrassar/TelegramBotAPI
Updating status of tgbotapi environment:
β PlaguBot (0.3.1)
β Libraries (0.0.11)
β CaptchaPlaguBotPlugin (0.1.6)
β PlaguBot (0.3.1)
β Libraries (0.0.11)
β CaptchaPlaguBotPlugin (0.1.6)
GitHub
GitHub - InsanusMokrassar/PlaguBot: Plugins-oriented bot
Plugins-oriented bot. Contribute to InsanusMokrassar/PlaguBot development by creating an account on GitHub.
Hi, new update 0.35.2 is dependencies-update release for now, but you may suggest some improvements in the comments or chat and make that release something more than just a dependencies actualization update π
GitHub
0.35.2 by InsanusMokrassar Β· Pull Request #428 Β· InsanusMokrassar/TelegramBotAPI
Hello everybody :) I have started 0.35.3 PR and wished to ask you a small question. Currently in
BehaviourBuilder waiters (wait* syntax) usually used mappers instead of filters (for example, for CallbackQuery you must return CallbackQuery of the same type or null instead of just Boolean). I want to replace this syntax with filters (just like in on* syntax). How do you think this change will affect your code? Will this break a lot of or maybe you wish this change will happen? Lets talk about this in comments to the next pollGitHub
0.35.3 by InsanusMokrassar Β· Pull Request #436 Β· InsanusMokrassar/TelegramBotAPI