Add is_direct to member event spec.

8 years ago · 8fe8bd6a81
parent 5fedc64230
commit 8fe8bd6a81
2 changed files with 5 additions and 1 deletions
--- a/api/client-server/create_room.yaml
+++ b/api/client-server/create_room.yaml
@ -180,7 +180,8 @@ paths:
                  synchronised at first. Both users may subsequently choose to
                  tag the room differently.
                  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:
        200:
          description: Information about the newly created room.
--- a/event-schemas/schema/m.room.member
+++ b/event-schemas/schema/m.room.member
@ -39,6 +39,9 @@ properties:
          - leave
          - ban
        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:
        properties:
          display_name: