lda/telodendria
lda/telodendria
1
1
Fork 1
forked from Telodendria/Telodendria
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
telodendria/Schema/SyncResponse.json

114 lines
2.5 KiB
JSON
Raw Normal View History

[WIP] Start making bare-bones /sync reply schema.
2024-06-09 00:13:49 +00:00
{
"guard": "TELODENDRIA_SCHEMA_SYNCRESPONSE_H",
"header": "Schema\/SyncResponse.h",
"types": {
"Event": {
"fields": {
"content": {
"type": "object",
"required": true
},
"type": {
"type": "string",
"required": true
}
},
"type": "struct"
},
"AccountData": {
"fields": {
"events": { "type": "[Event]" }
},
"type": "struct"
},
[ADD/WIP] Start /messages, sync timeouts, cleaning This code _really_ isn't good. I've spotted some fun racing happen and leak of some JSON(somehow?) without timeout, and I've been trying to spend the last several days trying to fix that. The good news is that, with some endpoint spoofing, you can actually _try_ this with a Matrix client(dev.cinny.in for example). I might consider rewriting this pastacode, considering the issues noted above in favour of a better design, with less odds of this.
2024-06-14 21:30:35 +00:00
"InviteState": {
[WIP] Start making bare-bones /sync reply schema.
2024-06-09 00:13:49 +00:00
"fields": {
[ADD/WIP] Start /messages, sync timeouts, cleaning This code _really_ isn't good. I've spotted some fun racing happen and leak of some JSON(somehow?) without timeout, and I've been trying to spend the last several days trying to fix that. The good news is that, with some endpoint spoofing, you can actually _try_ this with a Matrix client(dev.cinny.in for example). I might consider rewriting this pastacode, considering the issues noted above in favour of a better design, with less odds of this.
2024-06-14 21:30:35 +00:00
"events": { "type": "[StrippedStateEvent]" }
[WIP] Start making bare-bones /sync reply schema.
2024-06-09 00:13:49 +00:00
},
"type": "struct"
},
[ADD/WIP] Start /messages, sync timeouts, cleaning This code _really_ isn't good. I've spotted some fun racing happen and leak of some JSON(somehow?) without timeout, and I've been trying to spend the last several days trying to fix that. The good news is that, with some endpoint spoofing, you can actually _try_ this with a Matrix client(dev.cinny.in for example). I might consider rewriting this pastacode, considering the issues noted above in favour of a better design, with less odds of this.
2024-06-14 21:30:35 +00:00
"States": {
"fields": {
[FIX] Make Telodendria play ball with Schildi The web versions worked fine, but the old Android ones tend to be strict, which is a great tool for testing.
2024-11-23 13:20:32 +00:00
"events": { "type": "array" }
[ADD/WIP] Start /messages, sync timeouts, cleaning This code _really_ isn't good. I've spotted some fun racing happen and leak of some JSON(somehow?) without timeout, and I've been trying to spend the last several days trying to fix that. The good news is that, with some endpoint spoofing, you can actually _try_ this with a Matrix client(dev.cinny.in for example). I might consider rewriting this pastacode, considering the issues noted above in favour of a better design, with less odds of this.
2024-06-14 21:30:35 +00:00
},
"type": "struct"
},
"StrippedStateEvent": {
[WIP] Start making bare-bones /sync reply schema.
2024-06-09 00:13:49 +00:00
"fields": {
"content": {
"type": "object",
"required": true
},
"sender": {
"type": "string",
"required": true
},
"state_key": {
"type": "string",
"required": true
},
"type": {
"type": "string",
"required": true
}
},
"type": "struct"
},
"InvitedRooms": {
"fields": {
"invite_state": { "type": "InviteState" }
},
"type": "struct"
},
"ClientEventWithoutRoomID": {
"fields": {
"content": { "type": "object", "required": true },
"event_id": { "type": "string", "required": true },
"origin_server_ts": { "type": "integer", "required": true },
"sender": { "type": "string", "required": true },
"state_key": { "type": "string" },
[MOD] Fix out redacts a bit
2024-09-14 18:00:32 +00:00
"redacts": { "type": "string" },
[WIP] Start making bare-bones /sync reply schema.
2024-06-09 00:13:49 +00:00
"type": { "type": "string", "required": true }
},
"type": "struct"
},
"Timeline": {
"fields": {
"events": { "type": "[ClientEventWithoutRoomID]", "required": true },
"limited": { "type": "boolean" },
"prev_batch": { "type": "string" }
},
"type": "struct"
},
"JoinedRooms": {
"fields": {
[ADD/WIP] Start /messages, sync timeouts, cleaning This code _really_ isn't good. I've spotted some fun racing happen and leak of some JSON(somehow?) without timeout, and I've been trying to spend the last several days trying to fix that. The good news is that, with some endpoint spoofing, you can actually _try_ this with a Matrix client(dev.cinny.in for example). I might consider rewriting this pastacode, considering the issues noted above in favour of a better design, with less odds of this.
2024-06-14 21:30:35 +00:00
"timeline": { "type": "Timeline" },
"state": { "type": "States" }
[WIP] Start making bare-bones /sync reply schema.
2024-06-09 00:13:49 +00:00
},
"type": "struct"
},
"Rooms": {
"fields": {
[MOD] Use keyed schemas for the sync
2024-08-27 16:56:38 +00:00
"invite": { "type": "{InvitedRooms}" },
"join": { "type": "{JoinedRooms}" }
[WIP] Start making bare-bones /sync reply schema.
2024-06-09 00:13:49 +00:00
},
"type": "struct"
},
"SyncResponse": {
"fields": {
"next_batch": {
"type": "string",
"required": true
},
"account_data": {
"type": "AccountData"
},
"rooms": {
"type": "Rooms"
}
},
"type": "struct"
}
}
}
Reference in a new issue Copy permalink