s/private_user_data/account_data/

pull/977/head
Mark Haines 9 years ago
parent 24c4b8b095
commit 40f7eab73f

@ -131,7 +131,7 @@ paths:
"type": "m.presence" "type": "m.presence"
} }
], ],
"private_user_data": [ "account_data": [
{ {
"type": "org.example.custom.config", "type": "org.example.custom.config",
"content": { "content": {

@ -24,7 +24,7 @@ paths:
description: |- description: |-
Set some config for the client. This config is only visible to the user Set some config for the client. This config is only visible to the user
that set the config. The config will be synced to clients in the that set the config. The config will be synced to clients in the
top-level ``private_user_data``. top-level ``account_data``.
security: security:
- accessToken: [] - accessToken: []
parameters: parameters:
@ -63,7 +63,7 @@ paths:
description: |- description: |-
Set some config for the client on a given room. This config is only Set some config for the client on a given room. This config is only
visible to the user that set the config. The config will be synced to visible to the user that set the config. The config will be synced to
clients in the per-room ``private_user_data``. clients in the per-room ``account_data``.
security: security:
- accessToken: [] - accessToken: []
parameters: parameters:

@ -233,7 +233,7 @@ paths:
} }
] ]
}, },
"private_user_data": { "account_data": {
"events": [ "events": [
{ {
"type": "org.example.custom.config", "type": "org.example.custom.config",

@ -12,11 +12,11 @@ The config may be either global or scoped to a particular rooms.
Events Events
------ ------
The client recieves the config as a event in the ``private_user_data`` sections The client recieves the config as a event in the ``account_data`` sections
of a v2 /sync. of a v2 /sync.
These events can also be received in a v1 /events response or in the These events 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 events appearing in v1 /events will have a ``room_id`` with the room
the tags are for. the tags are for.

Loading…
Cancel
Save