wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Note that m.tag events can appear in v1 initialSync and /events as well as v2 sync. Only add the room_id for v1 /events since it is redundant in v1 /initialSync

Browse source
This commit is contained in:
Mark Haines 2015-11-02 10:13:47 +00:00
parent ad86426e95
commit f557e69860
2 changed files with 8 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

3
api/client-server/v1/sync.yaml
View file

@ -248,8 +248,7 @@ paths:
"visibility": "private", "visibility": "private",
"private_user_data": [{ "private_user_data": [{
"type": "m.tag", "type": "m.tag",
"content": {"tags": ["work"]}, "content": {"tags": ["work"]}
"room_id": "!TmaZBKYIFrIPVGoUYp:localhost"
}] }]
} }
] ]

9
specification/modules/tags.rst
View file

@ -10,8 +10,13 @@ user that set them but are shared across all their devices.
Events Events
------ ------
The tags on a room are passed as single ``m.tag`` event in the The tags on a room are receieved as single ``m.tag`` event in the
``private_user_data`` section of a room in v2 sync. ``private_user_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``
events appearing in v1 /events will have a ``room_id`` with the room
the tags are for.
{{m_tag_event}} {{m_tag_event}}