We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to run the example in the readme results in a broken build:
Resolving dependencies Fetching https://github.com/protoncr/tourmaline.git Fetching https://github.com/crystal-lang/crystal-db.git Fetching https://github.com/mamantoha/http_proxy.git Using db (0.11.0) Using http_proxy (0.10.3 at ea17189) Installing tourmaline (0.29.0 at 08717e7) Writing shard.lock Building: bot Error target bot failed to compile: Showing last frame. Use --error-trace for full trace. In lib/tourmaline/src/tourmaline/context.cr:69:17 69 | @client.send_message(**kwargs, chat_id: message.chat.id, text: text) ^----------- Error: no parameter named 'reply_to_message_id' Overloads are: - Tourmaline::Client::Api#send_message(chat_id : Int32 | Int64 | String, text : String, message_thread_id : Int32 | Int64 | ::Nil = nil, parse_mode : ParseMode = default_parse_mode, entities : Array(Tourmaline::MessageEntity) | ::Nil = nil, link_preview_options : Tourmaline::LinkPreviewOptions | ::Nil = nil, disable_notification : Bool | ::Nil = nil, protect_content : Bool | ::Nil = nil, reply_parameters : Tourmaline::ReplyParameters | ::Nil = nil, reply_markup : Tourmaline::InlineKeyboardMarkup | Tourmaline::ReplyKeyboardMarkup | Tourmaline::ReplyKeyboardRemove | Tourmaline::ForceReply | ::Nil = nil)
Seems to be related to #68, 5772091 seems to be working fine.
The text was updated successfully, but these errors were encountered:
https://core.telegram.org/bots/api-changelog#december-29-2023
Sorry, something went wrong.
No branches or pull requests
Trying to run the example in the readme results in a broken build:
Seems to be related to #68, 5772091 seems to be working fine.
The text was updated successfully, but these errors were encountered: