From 85bd4a3e1fc28c5325b8e53dec4d050f669ea074 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Mon, 28 Mar 2022 18:27:48 +0200 Subject: [PATCH] events: Document the unstable-extensible-events feature --- crates/ruma-common/src/events/message.rs | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/crates/ruma-common/src/events/message.rs b/crates/ruma-common/src/events/message.rs index a6c8439e..80bac7f4 100644 --- a/crates/ruma-common/src/events/message.rs +++ b/crates/ruma-common/src/events/message.rs @@ -21,8 +21,10 @@ //! //! # How to use them //! -//! First, enable the `unstable-mscXXXX` features (where `XXXX` is the number of the MSC) for the -//! needed extensible types. +//! First, you can enable the `unstable-extensible-events` feature from the `ruma` crate, that +//! will enable all the MSCs for the extensible events that correspond to the legacy `msgtype`s +//! (1767, 3246, 3488, 3551, 3552, 3553). It is also possible to enable only the MSCs you want with +//! the `unstable-mscXXXX` features (where `XXXX` is the number of the MSC). //! //! The recommended way to send transitional extensible events while they are unstable and during //! the transition period is to build one of the new primary types and then to convert it to a