Need to add scope parameter to manual mode commands for consistency with annotation mode.

Parameter name must be corrected according to the api.

actually sent message:
"reply_markup":{"input_field_place_holder":
telegram bot api:
"input_field_placeholder":

Strange behaviour with coroutines on 5.x.x versions due to moving to multiplatfrom.
Need to do more detailed check and find solution.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Describe the bug

The proposed webhook handling approach is not suitable because it suggests assigning processing behavior in a controller.
So it would lead to defining the processing behavior every time.

Expected behavior

Reorganize update processing and make it more flexible.

Describe the bug
If I use \s in command like @RegexCommandHandler("/go\\s") I get a compilation error

Expected behavior
The string remains as is in the generated code and does not lead to a compilation error

I assume that the issue is code is generated somehow manually instead of using specialized libraries like KotlinPoet

Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to define conversations using input handlers.
When you are using input handlers, it's pretty hard to write and manage complex conversations.

Describe the solution you'd like
Instead of input handlers, we could use classes for defining conversations. So we are able to write more well-architected code, even when it is complex.

Example:

package com.example.blank.conversation

import eu.vendeli.tgbot.TelegramBot
import eu.vendeli.tgbot.api.message
import eu.vendeli.tgbot.types.User
import eu.vendeli.tgbot.types.internal.ProcessedUpdate

sealed class GreetingsConversation {
    object Start : GreetingsConversation() {
        fun handle(update: ProcessedUpdate, user: User, bot: TelegramBot) {
            message("Hello, let's move to second step!").send(user, bot)
            //set secondStep state
           //maybe something like 
           setData(user, "hello" to update.text)
           setState(user, GreetingsConversation::start)
        }
    }

    object SecondStep : GreetingsConversation() {
        fun handle(update: ProcessedUpdate, user: User, bot: TelegramBot) {
            // retrieve data from start step and proceed
            message("Nice job! You completed this.").send(user, bot)
            deleteState(user, GreetingsConversation)
        }
    }
}

Additional context
Not sure, if we can do this way.
We discussed about it in Telegram group.

Increase test coverage, create a more convenient flow of tests.

• Cover with tests api methods as much as possible.

Need to change the get method of an object into a suspend function to improve asynchrony.

Describe the bug
I've added a non-private helper method to a controller. I didn't make it private by mistake, but this occasion made TelegramActionsCollector find a total of 2 actions instead of 6 expected. So I commented out this new method and then all actions were found. I didn't find any documentation on that case, so I suppose it isn't intended behavior

To Reproduce

1. Create controller with an action. Make sure your action is found during start-up process
2. Add another public method to your controller
3. Not during start-up, your action won't be found

Expected behavior
I expect that any amount of public/private methods could be added to controller without interfering with work of telegram bot api library

Screenshots

With public helper method, 2 actions in total

With private helper method, 6 actions in total

Additional context
No stacktrace or error log were produced
P.S. I do enjoy your lib

Describe the bug
I created sample application and run it from IntelliJ IDEA. Bot works few seconds and replies on commands. But CPU utilization is very high memory usage is increasing

To Reproduce
Steps to reproduce the behavior:

1. Try to create sample application
2. Just wait for 10 seconds after bot starts
3. Bot becomes non-responsible

Expected behavior
Bot is able to reply on commands unless application is running

Settings
JDK 21
build.gradle.kts (also tried to switch to 1.9.22):

plugins {
    kotlin("jvm") version "1.9.21"
    id("com.google.devtools.ksp") version "1.9.21-1.0.15"
}

dependencies {
    implementation("eu.vendeli:telegram-bot:4.3.0")
    ksp("eu.vendeli:ksp:4.3.0")
}

main.kt (it doesn't matter if any command is defined):

suspend fun main() {
    val bot = TelegramBot(TOKEN) {
        logging {
            botLogLevel = LogLvl.DEBUG
        }
    }

    bot.handleUpdates()
}

@CommandHandler(["/start"])
suspend fun start(user: User, bot: TelegramBot) {
    message { "Hello Human" }.send(user, bot)
}

Additional context
Logs:

18:29:10.517 [main] INFO eu.vendeli.tgbot.core.TgUpdateHandler -- 
CommandHandlers:
(/start, message) - InvocationMeta(qualifier=, function=start, rateLimits=RateLimits(period=0, rate=0))
InputHandlers:
None
RegexCommandHandlers:
None
UpdateTypeHandlers:
None
UnprocessedHandler:
None
18:29:10.522 [main] DEBUG eu.vendeli.tgbot.core.TgUpdateHandler -- The listener is stopped.
18:29:10.523 [main] DEBUG eu.vendeli.tgbot.core.TgUpdateHandler -- The listener is set.
18:29:10.523 [main] DEBUG eu.vendeli.tgbot.core.TgUpdateHandler -- Starting updates collector.
18:29:10.524 [main] INFO eu.vendeli.tgbot.core.TgUpdateHandler -- Starting long-polling listener.
18:29:10.527 [DefaultDispatcher-worker-1] DEBUG eu.vendeli.tgbot.core.TgUpdateHandler -- Running listener with offset - 0
18:29:12.276 [DefaultDispatcher-worker-1] DEBUG eu.vendeli.tgbot.TelegramBot -- RequestBody: {"offset":0,"timeout":20}
18:29:34.885 [DefaultDispatcher-worker-50] DEBUG eu.vendeli.tgbot.core.TgUpdateHandler -- Running listener with offset - 0
18:29:34.885 [DefaultDispatcher-worker-50] DEBUG eu.vendeli.tgbot.TelegramBot -- RequestBody: {"offset":0,"timeout":20}
18:30:00.283 [DefaultDispatcher-worker-29] DEBUG eu.vendeli.tgbot.core.TgUpdateHandler -- Running listener with offset - 0
18:30:00.283 [DefaultDispatcher-worker-29] DEBUG eu.vendeli.tgbot.TelegramBot -- RequestBody: {"offset":0,"timeout":20}

In docs there is a way to set custom implementation of userData, but userData is internal and this can not be modified.

The input must be repeated after an unsuccessful attempt.

When I want use library in SpringBoot, to make library's DI works with SpringBoot‘s DI, I have to write:

@Configuration
class BeanCreator(
    @Value("\${telegram.bot.token:}")
    private val botToken: String,
    private val context: ConfigurableApplicationContext
) {
    @Bean
    fun getBot(): TelegramBot {
        val bot = TelegramBot(botToken, "xxx.botController") {
            classManager = object : ClassManager {
                private val instances by lazy { mutableMapOf<String, Any>() }
                override fun getInstance(clazz: Class<*>, vararg initParams: Any?): Any =
                    context.getBean(clazz)?: instances.getOrElse(clazz.name) {
                        if (initParams.isEmpty()) clazz.declaredConstructors.first().newInstance()
                        else {
                            clazz.declaredConstructors.first().newInstance(initParams)
                        }.also { instances[clazz.name] = it }
                    }
            }
        }
        bot.update.setBehaviour {
            handle(it)
        }
        return bot
    }
}

In this case, I want to provide a ClassManager but don't acturally want to implement the ClassManager.
Maybe we should make ClassManagerImpl open so that users can inherit the class to make small modification. In this case, the code could be write as following:

@Configuration
class BeanCreator(
    @Value("\${telegram.bot.token:}")
    private val botToken: String,
    private val context: ConfigurableApplicationContext
) {
    @Bean
    fun getBot(): TelegramBot {
        val bot = TelegramBot(botToken, "xxx.botController") {
            classManager = object : ClassManagerImpl {
                override fun getInstance(clazz: Class<*>, vararg initParams: Any?): Any =
                    context.getBean(clazz)?: super.getInstance(clazz,initParams)
            }
        }
        bot.update.setBehaviour {
            handle(it)
        }
        return bot
    }
}
// I'm not quite familiar with kotlin, so I'm not sure this code could work.

Anyway, maybe this code can add into the SpringBoot demo to show how to work with SpringBoot?

I would like to add an API for setting network proxies, which is important in some cases. Please consider this. Thank you.

Hello,

Firstly, I want to commend you on the excellent work you've done with this project.
Secondly, I have a question: Is it possible to send a video or photo using a fileId instead of uploading it each time? Are there any options available for this?

If the file is already stored somewhere on the Telegram servers, you don't need to reupload it: each file object has a file_id field, simply pass this file_id as a parameter instead of uploading. There are no limits for files sent this way.

Thank you.

Come up with a flexible mechanism for parsing a command through a tree of characters.

Describe the bug

The following code can't work as expected.

setWebhook("https://site.com/bots").options {
  certificate = ResourceUtils.getFile("classpath:site.com.pem")
}.send(bot)

Telegram need inputfile but we provided the local path of the file.

To Reproduce

setWebhook("https://site.com/bots").options {
  certificate = ResourceUtils.getFile("classpath:site.com.pem")
}.send(bot)

https://api.telegram.org/bot[TOKEN]/getwebhookinfo: "has_custom_certificate":false, is always false.

Hello,
I've already tried .js implementations and nodejs http request to get some positive result when using setMyCommands. The request/response says O.K. but nothing was changed (tried several settings with @telegram‧botFather on my bot, as well).

If telegram-bot can show that setMyCommands works, I would have to switch to Kotlin.

P.S. clever, the interface BotWaitingInput

link: https://github.com/vendelieu/telegram-bot/wiki/Updates-handling#handling-updates-by-its-type
Bug: ProcessedUpdate don't have User, so

@UpdateHandler([UpdateType.MESSAGE])
suspend fun handleAllMessages(update: ProcessedUpdate, bot: TelegramBot) {
    message { "Hello" }.send(update.user, bot)
}

can't compile.

[Affect method] declineChatJoinRequest and approveChatJoinRequest and ?(Maybei more)

[Suggestion] Parameter for User and Chat following convention：

• type String: username (@ghost);
• type Long: user ID / chat ID;
• type User/Chat: the object.
• We'd better provide 2 method for each API: [type String + type User/Chat] / [type Long + type User/Chat], with type User/Chat, we parse necessary parameter in library.

[Step] Maybe we should slow update this:

1. Mark the origin API as deprecated, develop new API and suggest them.
2. Maintain all APIs in some versions.
3. Delete the deprecated API and release a big version.

I am trying to send message in next way:

        val id = "some_id"
        message {
            "Your id:" - code { id }
        }.options {
            parseMode = ParseMode.MarkdownV2
        }.markup {
            inlineKeyboardMarkup {
                "Yes" callback "a"
                "No" callback "b"
            }
        }.send(user, bot)

I want my message look like:

Your id: some_id
[Yes][No]

And I can achieve that by manually wrapping strings in proper symbols, but I want to know how to use EntitiesContextBuilder functions and are they supposed to be used for that purpose?

Thanks in advance :)

Issue with Voice type deserialization because of wrong mimeType type.

Delete BotUserData, BotChatData, BotInputListener to get rid of Bot* prefix since it's redundant.

Add mirror documentation for telegram api methods to make method hints more indicative.

All telegram api methods can be found in api directory.

Also, when copying documentation from telegram api, do not forget to change the format of api parameters from snake_case to camelCase.

The basic ClassicManagerImpl in some environments takes an empty list as an argument and gives IllegalArgumentException wrong number of arguments.

To Reproduce
Steps to reproduce the behavior:
I used to get this behavior when trying to deplocate a bot on a heroku.

Expected behavior
The same work of designers in all environments

Add a basic implementation for the convenience of the initial experience.