Clarify that an `m.room.name` event with an absent `name` field is not expected behavior (#1639)

Fixes #1632

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
pull/1645/head
Kévin Commaille 1 year ago committed by GitHub
parent 838dec272c
commit 044a78730e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -0,0 +1 @@
Clarify that an `m.room.name` event with an absent `name` field is not expected behavior.

@ -7,9 +7,8 @@ description: |-
is a human-friendly string designed to be displayed to the end-user. The 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. 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 If a room has an `m.room.name` event with an absent, null, or empty `name`
`name` field should be treated the same as a room with no `m.room.name` field, it should be treated the same as a room with no `m.room.name` event.
event.
An event of this type is automatically created when creating a room using An event of this type is automatically created when creating a room using
`/createRoom` with the `name` key. `/createRoom` with the `name` key.

Loading…
Cancel
Save