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>
This commit is contained in:
parent
838dec272c
commit
044a78730e
2 changed files with 3 additions and 3 deletions
|
@ -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.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue