-
Notifications
You must be signed in to change notification settings - Fork 232
Room navigation #2695
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
Room navigation #2695
Conversation
… managing different routes
📱 Scan the QR code below to install the build (arm64 only) for this PR. |
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.
|
I am trying to figure out why the Also, the code coverage is not good (-0.45%), this is related to the issue above, but not only. Regarding the timing, we need to merge the PR. We will investigate the coverage issue later. |
Type of change
Content
This PR introduces a
JoinedRoomFlowNode
which is the previousRoomFlowNode
.RoomFlowNode
is now responsible to listen on room membership to decide which node to render, eitherJoinedRoomFlowNode
or the newJoinRoomNode
.The
JoinRoomNode
is not completed yet, but this is a first draft.Motivation and context
Closes #2654
Closes #2658
Handles some part of element-hq/element-meta#2341
Screenshots / GIFs
Tests
Tested devices
Checklist