f923d08078
This is the spec for https://github.com/matrix-org/matrix-doc/issues/910 Fixes https://github.com/matrix-org/matrix-doc/issues/910 Some reverse engineering was required to work out the complete details as to how this works. In particular, the 405 for setting account data and the behaviour of m.read. References: * 405 for account data:d69decd5c7/synapse/rest/client/v2_alpha/account_data.py (L85-L90)* m.read behaviour:d69decd5c7/synapse/rest/client/v2_alpha/read_marker.py (L45-L52)
29 lines
939 B
Text
29 lines
939 B
Text
{
|
|
"type": "object",
|
|
"title": "Read Marker Location Event",
|
|
"description": "The current location of the user's read marker in a room. This event appears in the user's room account data for the room the marker is applicable for.",
|
|
"allOf": [{
|
|
"$ref": "core-event-schema/event.yaml"
|
|
}],
|
|
"properties": {
|
|
"content": {
|
|
"type": "object",
|
|
"properties": {
|
|
"event_id": {
|
|
"type": "string",
|
|
"description": "The event the user's read marker is located at in the room."
|
|
}
|
|
},
|
|
"required": ["event_id"]
|
|
},
|
|
"type": {
|
|
"type": "string",
|
|
"enum": ["m.fully_read"]
|
|
},
|
|
"room_id": {
|
|
"type": "string",
|
|
"description": "The room ID the read marker applies to."
|
|
}
|
|
},
|
|
"required": ["type", "room_id", "content"]
|
|
}
|