From 897146e369e5f4e08729c7f1c781ea8be7e20ba3 Mon Sep 17 00:00:00 2001 From: Jonas Platte Date: Fri, 19 Nov 2021 10:49:11 +0100 Subject: [PATCH] events: Fix some docs being on wrong constructor --- crates/ruma-events/src/room/message.rs | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/crates/ruma-events/src/room/message.rs b/crates/ruma-events/src/room/message.rs index b5f0633c..08f4930c 100644 --- a/crates/ruma-events/src/room/message.rs +++ b/crates/ruma-events/src/room/message.rs @@ -125,11 +125,6 @@ impl RoomMessageEventContent { } /// Creates a plain text notice reply to a message. - /// - /// Different from `notice_reply_plain`, this constructor requires specifically a - /// [`RoomMessageEvent`] since it creates a permalink to the previous message, for which the - /// room ID is required. If you want to reply to a [`SyncRoomMessageEvent`], you have to convert - /// it first by calling [`.into_full_event()`][crate::SyncMessageEvent::into_full_event]. pub fn notice_reply_plain( reply: impl fmt::Display, original_message: &impl ReplyBaseEvent, @@ -146,6 +141,11 @@ impl RoomMessageEventContent { } /// Creates a html text notice reply to a message. + /// + /// Different from `notice_reply_plain`, this constructor requires specifically a + /// [`RoomMessageEvent`] since it creates a permalink to the previous message, for which the + /// room ID is required. If you want to reply to a [`SyncRoomMessageEvent`], you have to convert + /// it first by calling [`.into_full_event()`][crate::SyncMessageEvent::into_full_event]. pub fn notice_reply_html( reply: impl fmt::Display, html_reply: impl fmt::Display,