Show a clear message/view when the user is no longer a joined member of a room (after leaving or getting kicked/banned)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by reading the RoomScreen and RoomsList behavior, then compare the membership-state logic in AddRoomScreen with the TombstoneFooter in RoomInputBar and the full-view pattern in InviteScreen. Decide which proposed design fits, then ensure removed users see an accurate left, kicked, or banned state and cannot interact as joined members, with re-join or knock actions when permitted.
由索引模型根据 Issue 内容生成。
描述
If the current user is removed (kicked or banned) from a joined room while that room is currently open in Robrix, then the RoomScreen should be updated to reflect that they are no longer a part of that room. Currently, the room is properly removed from the RoomsList, but the RoomScreen itself does not change, which is likely confusing to the user as it looks like they are still a joined member of the room and able to interact within it.
There are two possible designs we could adopt here:
- Show a footer, similar to the
TombstoneFooterin theRoomInputBar, that displays the status of their membership in that room (whether they were joined or banned) and a button to re-join or knock on that room (if permitted).- This allows the user to still see the content of the room they were removed from, but not to send any messages.
- Hide the entire RoomScreen, and show only the content of the footer, but in a full view similar to the InviteScreen.
- This prevents the user from seeing the room at all once they are kicked/banned.
I think both approaches have their merits, but at this point I am slightly in favor of approach 1.
For determining what message and button text to show, see the related logic in the AddRoomScreen for determining whether a room is in the Left, Kicked, or Banned state for the current user.
- 主要语言
- Rust
- 星标
- 508
- 派生
- 72
- 平均合并
- 1 小时 43 分钟
- 30 天内合并 PR
- 131
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
project-robius/robrix 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 48/100
project-robius/robrix#1309 ·
维护者通常 1 天内回复
-
blocked-on-robius enhancement
难度 5/5 一周以上 新手友好度 35/100
project-robius/robrix#1269 · 1 条评论 ·
维护者通常 1 天内回复
-
blocked-on-makepad enhancement
难度 4/5 1-2 天 新手友好度 30/100
project-robius/robrix#1253 ·
维护者通常 1 天内回复
-
blocked-on-makepad enhancement
难度 5/5 一周以上 新手友好度 35/100
project-robius/robrix#1230 ·
维护者通常 1 天内回复
-
blocked-on-makepad enhancement
难度 5/5 一周以上 新手友好度 30/100
project-robius/robrix#1229 ·
维护者通常 1 天内回复
查看 project-robius/robrix 的全部 Issue
相似的 Issue
-
ai_p2
难度 2/5 1-3 小时 新手友好度 82/100
ClickHouse/ClickHouse#130006 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
horizon-rust/horizon#12071 ·
维护者通常 1 天内回复
-
bug priority: low
难度 2/5 1-3 小时 新手友好度 78/100
storytold/photocraft#12183 · 1 条评论 ·
维护者通常 2 天内回复
-
area:render needs-triage
难度 2/5 1-3 小时 新手友好度 78/100
bherbruck/solvecraft#13138 ·
-
testing
难度 2/5 1-3 小时 新手友好度 65/100