Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S2S v1 send_join: event response property not documented #1515

Open
joepie91 opened this issue May 8, 2023 · 3 comments
Open

S2S v1 send_join: event response property not documented #1515

joepie91 opened this issue May 8, 2023 · 3 comments
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@joepie91
Copy link

joepie91 commented May 8, 2023

Link to problem area: https://spec.matrix.org/v1.6/server-server-api/#put_matrixfederationv1send_joinroomideventid

Issue

Aside from auth_chain, origin, and state, the example response also shows an event property, but it is not specified what this is (although it seems to be the signed event generated by the resident homeserver).

As this is top-level in the response and not part of an event, it's not already covered by the various "event format may change" warnings, and indeed this does not seem to be specified in the room version spec either.

@joepie91 joepie91 added the clarification An area where the expected behaviour is understood, but the spec could do with being more explicit label May 8, 2023
@richvdh
Copy link
Member

richvdh commented May 9, 2023

I think the example is wrong here - it seems to have been added since v1.1, but send_join v1 shouldn't have changed.

@richvdh
Copy link
Member

richvdh commented May 9, 2023

(would be good to do some git archaeology to figure out when/why this changed)

@DMRobertson
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Development

No branches or pull requests

3 participants