Add is_direct to member event spec.
This commit is contained in:
parent
5fedc64230
commit
8fe8bd6a81
2 changed files with 5 additions and 1 deletions
|
@ -180,7 +180,8 @@ paths:
|
||||||
synchronised at first. Both users may subsequently choose to
|
synchronised at first. Both users may subsequently choose to
|
||||||
tag the room differently.
|
tag the room differently.
|
||||||
This adds an ``is_direct`` flag to the content of any invites
|
This adds an ``is_direct`` flag to the content of any invites
|
||||||
sent.
|
sent, which will appear in the content of the `m.room.member`_
|
||||||
|
event.
|
||||||
responses:
|
responses:
|
||||||
200:
|
200:
|
||||||
description: Information about the newly created room.
|
description: Information about the newly created room.
|
||||||
|
|
|
@ -39,6 +39,9 @@ properties:
|
||||||
- leave
|
- leave
|
||||||
- ban
|
- ban
|
||||||
type: string
|
type: string
|
||||||
|
is_direct:
|
||||||
|
description: Flag indicating if this room was created with the intention of being a direct chat
|
||||||
|
type: boolean
|
||||||
third_party_invite:
|
third_party_invite:
|
||||||
properties:
|
properties:
|
||||||
display_name:
|
display_name:
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue