-
Notifications
You must be signed in to change notification settings - Fork 52
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
Test MSC3083 - joining a restricted room. #98
Conversation
|
||
// Leaving the room works and the user is unable to re-join. | ||
bob.LeaveRoom(t, room) | ||
bob.LeaveRoom(t, space) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if you leave the space first?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leaving the space first should be fine. The ordering of these two steps doesn't matter.
Co-authored-by: Kegsay <[email protected]>
Although...I now realize that these tests aren't actually running due to matrix-org/pipelines#139, although they won't run anyway until Synapse opts into them. Seems like a chicken-and-egg problem to me. 😢 |
This tests matrix-org/synapse#9735 by creating a room that requires membership of a space to join, then attempts to join it (which will fail), then joins the space, then joins the room (which now succeeds).
See #93 for why this is being re-created.