1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

use super::{
    InputContactMessageContent, InputInvoiceMessageContent, InputLocationMessageContent,
    InputTextMessageContent, InputVenueMessageContent,
};

use serde::{Deserialize, Serialize};

/// This object represents the content of a message to be sent as a result of an inline query. Telegram clients currently support the following 5 types:
/// - [`InputTextMessageContent`]
/// - [`InputLocationMessageContent`]
/// - [`InputVenueMessageContent`]
/// - [`InputContactMessageContent`]
/// - [`InputInvoiceMessageContent`]
/// # Documentation
/// <https://core.telegram.org/bots/api#inputmessagecontent>
#[derive(Clone, Debug, PartialEq, Serialize, Deserialize)]
#[serde(untagged)]
pub enum InputMessageContent {
    Text(InputTextMessageContent),
    Location(InputLocationMessageContent),
    Venue(InputVenueMessageContent),
    Contact(InputContactMessageContent),
    Invoice(InputInvoiceMessageContent),
}

impl From<InputTextMessageContent> for InputMessageContent {
    fn from(val: InputTextMessageContent) -> Self {
        Self::Text(val)
    }
}

impl From<InputLocationMessageContent> for InputMessageContent {
    fn from(val: InputLocationMessageContent) -> Self {
        Self::Location(val)
    }
}

impl From<InputVenueMessageContent> for InputMessageContent {
    fn from(val: InputVenueMessageContent) -> Self {
        Self::Venue(val)
    }
}

impl From<InputContactMessageContent> for InputMessageContent {
    fn from(val: InputContactMessageContent) -> Self {
        Self::Contact(val)
    }
}

impl From<InputInvoiceMessageContent> for InputMessageContent {
    fn from(val: InputInvoiceMessageContent) -> Self {
        Self::Invoice(val)
    }
}