Struct botapi::gen_methods::CallSendDocument
source · pub struct CallSendDocument<'a> { /* private fields */ }
Implementations§
source§impl<'a> CallSendDocument<'a>
impl<'a> CallSendDocument<'a>
sourcepub fn chat_id(self, chat_id: i64) -> Self
pub fn chat_id(self, chat_id: i64) -> Self
Unique identifier for the target chat or username of the target channel (in the format @channelusername)
sourcepub fn message_thread_id(self, message_thread_id: i64) -> Self
pub fn message_thread_id(self, message_thread_id: i64) -> Self
Unique identifier for the target message thread (topic) of the forum; for forum supergroups only
sourcepub fn document(self, document: FileData) -> Self
pub fn document(self, document: FileData) -> Self
File to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More information on Sending Files: https://core.telegram.org/bots/api#sending-files
sourcepub fn thumbnail(self, thumbnail: FileData) -> Self
pub fn thumbnail(self, thumbnail: FileData) -> Self
Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail’s width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can’t be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More information on Sending Files: https://core.telegram.org/bots/api#sending-files
sourcepub fn caption(self, caption: &'a str) -> Self
pub fn caption(self, caption: &'a str) -> Self
Document caption (may also be used when resending documents by file_id), 0-1024 characters after entities parsing
sourcepub fn parse_mode(self, parse_mode: &'a str) -> Self
pub fn parse_mode(self, parse_mode: &'a str) -> Self
Mode for parsing entities in the document caption. See formatting options for more details.
sourcepub fn caption_entities(self, caption_entities: &'a Vec<MessageEntity>) -> Self
pub fn caption_entities(self, caption_entities: &'a Vec<MessageEntity>) -> Self
A JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
sourcepub fn disable_content_type_detection(
self,
disable_content_type_detection: bool
) -> Self
pub fn disable_content_type_detection( self, disable_content_type_detection: bool ) -> Self
Disables automatic server-side content type detection for files uploaded using multipart/form-data
sourcepub fn disable_notification(self, disable_notification: bool) -> Self
pub fn disable_notification(self, disable_notification: bool) -> Self
Sends the message silently. Users will receive a notification with no sound.
sourcepub fn protect_content(self, protect_content: bool) -> Self
pub fn protect_content(self, protect_content: bool) -> Self
Protects the contents of the sent message from forwarding and saving
sourcepub fn reply_to_message_id(self, reply_to_message_id: i64) -> Self
pub fn reply_to_message_id(self, reply_to_message_id: i64) -> Self
If the message is a reply, ID of the original message
sourcepub fn allow_sending_without_reply(
self,
allow_sending_without_reply: bool
) -> Self
pub fn allow_sending_without_reply( self, allow_sending_without_reply: bool ) -> Self
Pass True if the message should be sent even if the specified replied-to message is not found
sourcepub fn reply_markup(self, reply_markup: &'a EReplyMarkup) -> Self
pub fn reply_markup(self, reply_markup: &'a EReplyMarkup) -> Self
Additional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.