Make null m.room.name behaviour explicit
PR feedback
This commit is contained in:
parent
7b4c21fa77
commit
d724b6bf75
2 changed files with 5 additions and 4 deletions
|
@ -6,8 +6,8 @@ description: |-
|
|||
considered the canonical one. This could be for display purposes or as
|
||||
suggestion to users which alias to use to advertise the room.
|
||||
|
||||
A room with an ``m.room.canonical_alias`` event with an empty or absent
|
||||
``alias`` field should be treated the same as a room with no
|
||||
A room with an ``m.room.canonical_alias`` event with an absent, null, or
|
||||
empty ``alias`` field should be treated the same as a room with no
|
||||
``m.room.canonical_alias`` event.
|
||||
properties:
|
||||
content:
|
||||
|
|
|
@ -7,8 +7,9 @@ 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 or empty ``name`` field
|
||||
should be treated the same as a room with no ``m.room.name`` event.
|
||||
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.
|
||||
|
||||
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