Show a clear message/view when the user is no longer a joined member of a room (after leaving or getting kicked/banned)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Rust
- Estrellas
- 489
- Forks
- 71
- Merge medio
- 1 h 27 min
- PR fusionados (30 d)
- 72
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de project-robius/robrix
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
project-robius/robrix#1154 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
project-robius/robrix#1155 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 Medio día Aptitud para principiantes 12/100
project-robius/robrix#1153 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue help wanted
Dificultad 3/5 1-2 días Aptitud para principiantes 38/100
project-robius/robrix#1152 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 15/100
project-robius/robrix#1151 ·
Los mantenedores suelen responder en 1 día
Todos los issues de project-robius/robrix
Issues similares
-
[1.x Bug] run-operation --sql reports success but rolls back writes on transaction-capable adaptersAbiertotriage
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
dbt-labs/dbt#16784 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area:cli bug good first issue priority:medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
rtk-ai/rtk#4615 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bnv-manager-v2: accept_invite creates the Mailcow domain admin before the commitPosiblemente ocupada @myOmikron la tomó hoy. Abiertobug ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Windows: mio 1.2.3 named-pipe use-after-free panics the native IPC broker and hangs every toolAbiertoplatform:windows tool triaged wontfix
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
resources: add a regression test confirming admin mint still works after the #16 SAC handoffPosiblemente ocupada @Daniexie la tomó hoy. Abiertocontracts good first issue Stellar Wave
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
OlaGreat/starbound-realms#137 · 1 comentario ·