Clarification of /messages response format #3380
Labels
clarification
An area where the spec could do with being more explicit
Comments
pizzapim
added
the
clarification
richvdh
added a commit
that referenced
this issue
Feb 1, 2022
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.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Link to problem area:
https://matrix.org/docs/spec/client_server/r0.6.1#get-matrix-client-r0-rooms-roomid-messages
Issue
The response format for the /messages endpoint says that 'chunk' only contains a list of non-state events ([RoomEvent]), but 'chunk' can also contain state events. I suggest changing it to '[RoomEvent or RoomStateEvent]'.
The text was updated successfully, but these errors were encountered: