[Discover + Join/Leave] Bind leave and refresh seats
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- Medio día
- Aptitud para principiantes
- 58/100
Línea de trabajo
Start in lib/screens/sessions/session_detail_screen.dart, where the Leave action and the onLeave callback live, and read the join state added by #109 first, since this issue depends on it. Disable the action on tap, then set the membership to not joined and refresh the meeting's seat count from the server on success. On failure, keep the joined state, show "Couldn't leave. Try again.", and re-enable Leave. Done when flutter test test/screens/sessions/session_detail_screen_dp_d07_2_test.dart and flutter analyze pass for both outcomes.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What to build
Connect Leave to membership removal and refresh the meeting’s seat count. A failed removal must keep the student shown as joined.
Files
lib/screens/sessions/session_detail_screen.dart(extend the prerequisite’s file)- Starting example: lib/screens/home_screen.dart
Steps
- When Leave is tapped, disable repeats and wait for onLeave. On success, set the visible membership to not joined and refresh the meeting.
- On failure, keep the joined state and show “Couldn’t leave. Try again.” Re-enable the action for a retry.
- Use the refreshed server count for seats instead of subtracting locally. Check both successful and failed removal.
Example
Rejected leave retainsLeave action; successful leave refreshes and returnsJoin if session still open.
Check it works
In test/screens/sessions/session_detail_screen_dp_d07_2_test.dart, check the example above and the failure or limit described in the steps. Run flutter test test/screens/sessions/session_detail_screen_dp_d07_2_test.dart and flutter analyze.
Before starting
- #109 — Bind join and host-manage UI states
References
Assign yourself before starting, or comment to claim the issue. Project setup.
- Lenguaje dominante
- PLpgSQL
- Estrellas
- 0
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
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 DevDogsUGA/DogPack
-
polish
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
DevDogsUGA/DogPack#131 ·
-
polish
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
DevDogsUGA/DogPack#130 ·
-
moderation
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
DevDogsUGA/DogPack#119 ·
-
moderation
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
DevDogsUGA/DogPack#113 ·
-
discover
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
DevDogsUGA/DogPack#106 ·
Todos los issues de DevDogsUGA/DogPack
Issues similares
-
7.0
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
unoplatform/uno.extensions#3253 ·
Los mantenedores suelen responder en 1 día
-
ai-driven-qa bug claude Minor
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
linagora/twake-mail-admin#301 ·
Los mantenedores suelen responder en 1 día
-
Form: setAllValues does not re-render when passed the same values reference (react-form regression)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
obsidianmd/obsidian-clipper#996 ·
Los mantenedores suelen responder en 1 día
-
bug deadball
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
leggetter/leggetter.co.uk#100 ·
Los mantenedores suelen responder en 1 día