mirror of
https://github.com/matrix-org/matrix-spec
synced 2025-12-23 17:48:37 +01:00
36b02edfc2
Fixes #3305 Fixes #3380 The idea here is to better distinguish between a 'raw' event (as we send over the wire), and the 'serialised' format, as sent in responses to the C-S api and in `PUT /_matrix/app/v1/transactions/{txnId}`. It's made more complicated by the fact that there are _two_ serialisation formats, one used by `/sync` and `/notifications`, and one by everything else (the difference being whether `room_id` is included). In an ideal world, we wouldn't repeat `SerialisedEvent` every time it's used, and instead just link to the first reference, but that's a job for another day. Another job for another day is to get rid of things like `sync_state_event.yaml` (which is now used only in one place, so should be inlined.) |
||
|---|---|---|
| .. | ||
| errors | ||
| wellknown | ||
| auth_data.yaml | ||
| auth_response.yaml | ||
| client_device.yaml | ||
| client_event.yaml | ||
| client_event_without_room_id.yaml | ||
| cross_signing_key.yaml | ||
| device_keys.yaml | ||
| event_batch.yaml | ||
| event_filter.yaml | ||
| key_backup_data.yaml | ||
| openid_token.yaml | ||
| public_rooms_chunk.yaml | ||
| public_rooms_response.yaml | ||
| push_condition.yaml | ||
| push_rule.yaml | ||
| push_ruleset.yaml | ||
| request_email_validation.yaml | ||
| request_msisdn_validation.yaml | ||
| request_token_response.yaml | ||
| room_event_filter.yaml | ||
| room_key_backup.yaml | ||
| security.yaml | ||
| sso_login_flow.yaml | ||
| state_event_batch.yaml | ||
| sync_filter.yaml | ||
| third_party_signed.yaml | ||
| timeline_batch.yaml | ||
| user_identifier.yaml | ||