Struct conogram::methods::send_video_note::SendVideoNoteRequest

pub struct SendVideoNoteRequest<'a> { /* private fields */ }

As of v.4.0, Telegram clients support rounded square MPEG4 videos of up to 1 minute long. Use this method to send video messages. On success, the sent Message is returned.

Implementations

impl<'a> SendVideoNoteRequest<'a>

pub fn new( api: &'a API, chat_id: impl Into<ChatId>, video_note: impl Into<InputFile> ) -> Self

pub fn business_connection_id( self, business_connection_id: impl Into<String> ) -> Self

Unique identifier of the business connection on behalf of which the message will be sent

pub fn chat_id(self, chat_id: impl Into<ChatId>) -> Self

Unique identifier for the target chat or username of the target channel (in the format @channelusername)

pub fn message_thread_id(self, message_thread_id: impl Into<i64>) -> Self

Unique identifier for the target message thread (topic) of the forum; for forum supergroups only

pub fn video_note(self, video_note: impl Into<InputFile>) -> Self

Video note to send. Pass a file_id as String to send a video note that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. More information on Sending Files ». Sending video notes by a URL is currently unsupported

pub fn duration(self, duration: impl Into<i64>) -> Self

Duration of sent video in seconds

pub fn length(self, length: impl Into<i64>) -> Self

Video width and height, i.e. diameter of the video message

pub fn thumbnail(self, thumbnail: impl Into<InputFile>) -> 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 »

pub fn disable_notification(self, disable_notification: impl Into<bool>) -> Self

Sends the message silently. Users will receive a notification with no sound.

pub fn protect_content(self, protect_content: impl Into<bool>) -> Self

Protects the contents of the sent message from forwarding and saving

pub fn reply_parameters( self, reply_parameters: impl Into<ReplyParameters> ) -> Self

Description of the message to reply to

pub fn reply_markup(self, reply_markup: impl Into<ReplyMarkup>) -> Self

Additional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove a reply keyboard or to force a reply from the user. Not supported for messages sent on behalf of a business account

Trait Implementations

impl<'a> Clone for SendVideoNoteRequest<'a>

fn clone(&self) -> SendVideoNoteRequest<'a>

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl<'a, 'b> IntoFuture for &'b SendVideoNoteRequest<'a>

type IntoFuture = Pin<Box<dyn Future<Output = Result<<SendVideoNoteRequest<'a> as RequestT>::ReturnType, ConogramError>> + Send + 'b>>

Which kind of future are we turning this into?

type Output = <Pin<Box<dyn Future<Output = Result<<SendVideoNoteRequest<'a> as RequestT>::ReturnType, ConogramError>> + Send + 'b>> as Future>::Output

The output that the future will produce on completion.

fn into_future(self) -> Self::IntoFuture

Creates a future from a value.

impl<'a> IntoFuture for SendVideoNoteRequest<'a>

type IntoFuture = Pin<Box<dyn Future<Output = Result<<SendVideoNoteRequest<'a> as RequestT>::ReturnType, ConogramError>> + Send + 'a>>

Which kind of future are we turning this into?

type Output = <Pin<Box<dyn Future<Output = Result<<SendVideoNoteRequest<'a> as RequestT>::ReturnType, ConogramError>> + Send + 'a>> as Future>::Output

The output that the future will produce on completion.

fn into_future(self) -> Self::IntoFuture

Creates a future from a value.