From fa742be5b83b142fc2250ca8feea3e1c2208d38a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Mon, 18 Sep 2023 14:35:10 +0200 Subject: [PATCH] Clarify that an `m.room.name` event with an absent `name` field is not expected behavior MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes #1632 Signed-off-by: Kévin Commaille --- data/event-schemas/schema/m.room.name.yaml | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/data/event-schemas/schema/m.room.name.yaml b/data/event-schemas/schema/m.room.name.yaml index c9236de09..0b3b34dc2 100644 --- a/data/event-schemas/schema/m.room.name.yaml +++ b/data/event-schemas/schema/m.room.name.yaml @@ -7,9 +7,8 @@ description: |- is a human-friendly string designed to be displayed to the end-user. The room name is not unique, as multiple rooms can have the same room name set. - A room with an `m.room.name` event with an absent, null, or empty - `name` field should be treated the same as a room with no `m.room.name` - event. + If a room has an `m.room.name` event with an absent, null, or empty `name` + field, it should be treated the same as a room with no `m.room.name` event. An event of this type is automatically created when creating a room using `/createRoom` with the `name` key.