Make a sweet API

[pengrad]

Call all methods as bot methods:

SendResponse response = bot.sendMessage(chatId, "Hello")
        .parseMode(ParseMode.Markdown)
        .execute();

Async

bot.sendMessage(chatId, "Hello")
        .parseMode(ParseMode.Markdown)
        .execute(callback);

execute(callback) or execute(onSuccess, onFailure)?

[AlexSocol]

Think there should be both methods, first for those on j7 with anonymous inner classes and second for j8 coders, who can use lambdas (because two aic'es will look terrible) 🤔

[sintyaaaaaa]

Call all methods as bot methods:

SendResponse response = bot.sendMessage(chatId, "Hello")
        .parseMode(ParseMode.Markdown)
        .execute();

Async

bot.sendMessage(chatId, "Hello")
        .parseMode(ParseMode.Markdown)
        .execute(callback);

execute(callback) or execute(onSuccess, onFailure)?

[HarryZalessky]

I'll work on it :)

[HarryZalessky]

The change is ready guys :)

[rufus20145]

What is the purpose of these changes? In the current version, you can easily pick out a module in the bot that will send requests to BotAPI, taking into its restrictions and repeat them in case of errors e.g. The new version introduces coupling, which will make such a split very difficult. In addition, they are so breaking that all projects using this library will require large code changes.

As an example of this look at my bot. I split it into modules which process different types of updates received by bot and return requests that need to be executed. Executor module is not ready yet, but I`m working on it. Also these changes will create a lot of circular references in projects that are built in a similar way to my current one.