Add last_known_event_id property #3986
Conversation
| @@ -49,6 +49,7 @@ key | type | value | description | required | |||
| --- | --- | --- | --- | --- | |||
| `predecessor_room_id` | string | Room ID | A reference to the room that came before and was replaced by this room | yes | |||
| `via_servers` | [string] | List of server names | The servers to attempt to join the room through. These servers should be participating in the room to be useful. This option is necessary since room ID's are not routable on their own. | |||
| `last_known_event_id` | string | Event ID | The event ID of the last known event in the old room | |||
There was a problem hiding this comment.
Why is this useful? We should continue the conversation in #3946 (comment)
There was a problem hiding this comment.
@andybalaam Friendly poke to respond in the other thread ^ so we can close or merge this PR.
(we could close regardless in favor of just updating the original MSC after reaching a conclusion in that thread)
|
(both of you should also have push permissions on the MSC, and this seems small enough to fit into the "suggestions" feature on github: it's not cleart why this PR exists) |
Yeah I didn't think of using the suggestions feature. Is this PR's existence a problem? |
|
Not a problem, just slightly awkward for tracking purposes :D |
|
Closing in favour of further discussion on the MSC itself. |
As agreed here: #3946 (comment)