Updated CommandHandler

In a group chat, Telegram allows specifying the bot to receive commands sent by a user by appending "@BotUsername" in the command, while this feature is not working as expected currently in Telegrammer:

If the user specifies the bot, the CommandHandler considers it a different command with "@" in the command name. We need to manually add a new command "/originalCommand@botUsername" to support it, which could be somehow misleading since most users (at least me) of this package would normally consider this automatically handled.

Using the workaround in 1. would cause each command to be coded twice, which can be tedious and inelegant in cases where there are many commands in a CommandHandler.
Therefore, I added the ability of checking the bot specified to the CommandHandler. This change does not break the existing API but only asks the username of the bot in the initializer optionally, and should then handle things correctly as intended.

Telegram Bot API 4.6 update

1.0.0-alpha.3

Stable Release candidate

• Get rid of third party libraries
• Using only multipart-kit from Vapor
• Using new AsyncHTTPClient based on NIO 2.0
• Updated to latest version of Telegram API

Telegram API 4.3, bug fixes

• Added swift-log
• Minor improvements and bug fixes

New logging - apple/swift-log

0.5.2

Implemented JobQueue, added more examples

Added:

• BasicJobQueue, OnceJob, RepeatedJob, DailyJob
• SchedulerBot example, which demonstrate JobQueue works
• SpellCheckerBot example, which demonstrate how to use InlineKeyboardButton and CallbackQueryHandler

Support for Telegram Bot API 4.1

Full support for Telegram Bot API 4.1, compatibility with swift 5.0

Fix bug for sending InlineKeyboardMarkup and MaskPosition in a multipart message

0.4.4

Workaround for memory leaked HTTPClient

Temporarily switched from vapor/http to URLSession

HandlerQueue class methods improvements

Fixed

• HandlerQueue class methods improvements