-
Notifications
You must be signed in to change notification settings - Fork 158
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
Requirement of via
attribute for m.space.parent
and m.space.child
events
#433
Comments
@timegrid Hmm, I guess it's a matter of semantics. I'm tempted to say that if you're running into this problem in your client, that probably means you might want to ensure that |
I'll also quote MSC 1772 (the original spaces spec): https://github.com/matrix-org/matrix-spec-proposals/pull/1772/files#
|
Todo: this needs to be reverted to be compliant with: matrix-org/matrix-spec#1618 |
Thanks for the clarification. Just a remark: moment itself has not implemented spaces yet. The error message above was triggered by some event of another client "out there in the wild", so I assume, this might become a problem again. In that case I'll report back and we can evaluate, if that error should be better handled by all clients or nio itself. |
According to the matrix specs for space child/parent events, the
via
attribute can be omitted:m.space.parent
:When not present or invalid, the room is not considered to be part of the parent space
m.space.child
:When not present or invalid, the child room is not considered to be part of the space
The schema implementation defines it as required though. I just tested the new version
0.21.2
against moment and got one related error message:Is there any reason, why
via
is required?The text was updated successfully, but these errors were encountered: