s/private_user_data/account_data/

pull/977/head
Mark Haines 9 years ago
parent c77b22778f
commit fcbb985073

@ -312,7 +312,7 @@ paths:
}
],
"visibility": "private",
"private_user_data": [{
"account_data": [{
"type": "m.tag",
"content": {"tags": {"work": {"order": "1"}}}
}]
@ -375,7 +375,7 @@ paths:
description: |-
Whether this room is visible to the ``/publicRooms`` API
or not."
private_user_data:
account_data:
type: array
description: |-
The private data that this user has attached to this room.

@ -246,7 +246,7 @@ paths:
}
],
"visibility": "private",
"private_user_data": [{
"account_data": [{
"type": "m.tag",
"content": {"tags": {"work": {"order": "1"}}}
}]
@ -336,7 +336,7 @@ paths:
description: |-
Whether this room is visible to the ``/publicRooms`` API
or not."
private_user_data:
account_data:
type: array
description: |-
The private data that this user has attached to

@ -139,7 +139,7 @@ paths:
e.g. typing.
allOf:
- $ref: "definitions/event_batch.json"
private_user_data:
account_data:
title: Private User Data
type: object
description: |-
@ -287,7 +287,7 @@ paths:
}
]
},
"private_user_data": {
"account_data": {
"events": [
{
"type": "m.tags",

@ -11,10 +11,10 @@ Events
------
The tags on a room are received as single ``m.tag`` event in the
``private_user_data`` section of a room in a v2 /sync.
``account_data`` section of a room in a v2 /sync.
The ``m.tag`` can also be received in a v1 /events response or in the
``private_user_data`` section of a room in v1 /initialSync. ``m.tag``
``account_data`` section of a room in v1 /initialSync. ``m.tag``
events appearing in v1 /events will have a ``room_id`` with the room
the tags are for.

Loading…
Cancel
Save