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
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
//! Twitch-specifica that only appear on Twitch-specific messages/tags.

use std::fmt::{Display, Formatter};
use std::ops::Range;

#[cfg(feature = "with-serde")]
use {serde::Deserialize, serde::Serialize};

/// Set of information describing the basic details of a Twitch user.
#[derive(Debug, Clone, PartialEq, Eq)]
#[cfg_attr(feature = "with-serde", derive(Serialize, Deserialize))]
pub struct TwitchUserBasics {
    /// The user's unique ID, e.g. `103973901`
    pub id: String,
    /// The user's login name. For many users, this is simply the lowercased version of their
    /// (display) name, but there are also many users where there is no direct relation between
    /// `login` and `name`.
    ///
    /// A Twitch user can change their `login` and `name` while still keeping their `id` constant.
    /// For this reason, you should always prefer to use the `id` to uniquely identify a user, while
    /// `login` and `name` are variable properties for them.
    ///
    /// The `login` name is used in many places to refer to users, e.g. in the URL for their channel page,
    /// or also in almost all places on the Twitch IRC interface (e.g. when sending a message to a
    /// channel, you specify the channel by its login name instead of ID).
    pub login: String,
    /// Display name of the user. When possible a user should be referred to using this name
    /// in user-facing contexts.
    ///
    /// This value is never used to uniquely identify a user, and you
    /// should avoid making assumptions about the format of this value.
    /// For example, the `name` can contain non-ascii characters, it can contain spaces and
    /// it can have spaces at the start and end (albeit rare).
    pub name: String,
}

/// An RGB color, used to color chat user's names.
///
/// This struct's `Display` implementation formats the color in the way Twitch expects it for
/// the "Update User Chat Color" API method, i.e. uppercase hex RGB with a `#`, e.g.:
///
/// ```rust
/// use twitch_irc::message::RGBColor;
/// let color = RGBColor {
///     r: 0x12,
///     g: 0x00,
///     b: 0x0F
/// };
/// assert_eq!(color.to_string(), "#12000F");
/// ```
#[derive(Debug, Clone, Copy, PartialEq, Eq)]
#[cfg_attr(feature = "with-serde", derive(Serialize, Deserialize))]
pub struct RGBColor {
    /// Red component
    pub r: u8,
    /// Green component
    pub g: u8,
    /// Blue component
    pub b: u8,
}

impl Display for RGBColor {
    fn fmt(&self, f: &mut Formatter<'_>) -> std::fmt::Result {
        write!(f, "#{:0>2X}{:0>2X}{:0>2X}", self.r, self.g, self.b)
    }
}

/// A single emote, appearing as part of a message.
#[derive(Debug, Clone, PartialEq, Eq)]
#[cfg_attr(feature = "with-serde", derive(Serialize, Deserialize))]
pub struct Emote {
    /// An ID identifying this emote. For example `25` for the "Kappa" emote, but can also be non-numeric,
    /// for example on emotes modified using Twitch channel points, e.g.
    /// `301512758_TK` for `pajaDent_TK` where `301512758` is the ID of the original `pajaDent` emote.
    pub id: String,
    /// A range of characters in the original message where the emote is placed.
    ///
    /// As is documented on `Range`, the `start` index of this range is inclusive, while the
    /// `end` index is exclusive.
    ///
    /// This is always the exact range of characters that Twitch originally sent.
    /// Note that due to [a Twitch bug](https://github.com/twitchdev/issues/issues/104)
    /// (that this library intentionally works around), the character range specified here
    /// might be out-of-bounds for the original message text string.
    pub char_range: Range<usize>,
    /// This is the text that this emote replaces, e.g. `Kappa` or `:)`.
    pub code: String,
}

/// A single Twitch "badge" to be shown next to the user's name in chat.
///
/// The combination of `name` and `version` fully describes the exact badge to display.
#[derive(Debug, Clone, PartialEq, Eq)]
#[cfg_attr(feature = "with-serde", derive(Serialize, Deserialize))]
pub struct Badge {
    /// A string identifying the type of badge. For example, `admin`, `moderator` or `subscriber`.
    pub name: String,
    /// A (usually) numeric version of this badge. Most badges only have one version (then usually
    /// version will be `0` or `1`), but other types of badges have different versions (e.g. `subscriber`)
    /// to differentiate between levels, or lengths, or similar, depending on the badge.
    pub version: String,
}

/// Extract the `message_id` from a [`PrivmsgMessage`](crate::message::PrivmsgMessage) or directly
/// use an arbitrary [`String`] or [`&str`] as a message ID. This trait allows you to plug both
/// of these types directly into [`say_in_reply_to()`](crate::TwitchIRCClient::say_in_reply_to)
/// for your convenience.
///
/// For tuples `(&str, &str)` or `(String, String)`, the first member is the login name
/// of the channel the message was sent to, and the second member is the ID of the message
/// to be deleted.
///
/// Note that even though [`UserNoticeMessage`](crate::message::UserNoticeMessage) has a
/// `message_id`, you can NOT reply to these messages or delete them. For this reason,
/// `ReplyToMessage` is not implemented for
/// [`UserNoticeMessage`](crate::message::UserNoticeMessage).
pub trait ReplyToMessage {
    /// Login name of the channel that the message was sent to.
    fn channel_login(&self) -> &str;
    /// The unique string identifying the message, specified on the message via the `id` tag.
    fn message_id(&self) -> &str;
}

impl<C, M> ReplyToMessage for (C, M)
where
    C: AsRef<str>,
    M: AsRef<str>,
{
    fn channel_login(&self) -> &str {
        self.0.as_ref()
    }

    fn message_id(&self) -> &str {
        self.1.as_ref()
    }
}

#[cfg(test)]
mod tests {
    use crate::message::{IRCMessage, PrivmsgMessage, ReplyToMessage};
    use std::convert::TryFrom;

    #[test]
    pub fn test_reply_to_message_trait_impl() {
        // just making sure that DeleteMessage is implemented for all of these variants
        let _a: Box<dyn ReplyToMessage> = Box::new(("asd", "def"));
        let _b: Box<dyn ReplyToMessage> = Box::new(("asd".to_owned(), "def"));
        let _c: Box<dyn ReplyToMessage> = Box::new(("asd", "def".to_owned()));
        let d: Box<dyn ReplyToMessage> = Box::new(("asd".to_owned(), "def".to_owned()));

        assert_eq!(d.channel_login(), "asd");
        assert_eq!(d.message_id(), "def");
    }

    fn function_with_impl_arg(a: &impl ReplyToMessage) -> String {
        a.message_id().to_owned()
    }

    #[test]
    pub fn test_reply_to_message_trait_for_privmsg() {
        let src = "@badge-info=;badges=;color=#0000FF;display-name=JuN1oRRRR;emotes=;flags=;id=e9d998c3-36f1-430f-89ec-6b887c28af36;mod=0;room-id=11148817;subscriber=0;tmi-sent-ts=1594545155039;turbo=0;user-id=29803735;user-type= :jun1orrrr!jun1orrrr@jun1orrrr.tmi.twitch.tv PRIVMSG #pajlada :dank cam";
        let irc_message = IRCMessage::parse(src).unwrap();
        let msg = PrivmsgMessage::try_from(irc_message).unwrap();

        let msg_ref: &PrivmsgMessage = &msg; // making sure the trait is implemented for the ref as well
        assert_eq!(msg_ref.channel_login(), "pajlada");
        assert_eq!(msg_ref.message_id(), "e9d998c3-36f1-430f-89ec-6b887c28af36");
        // testing references work as arguments, as intended
        assert_eq!(
            function_with_impl_arg(msg_ref),
            "e9d998c3-36f1-430f-89ec-6b887c28af36"
        );
    }
}