Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Report & Block] Replace unavailable/quarantined session detail

Abierto
#121 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
dart
Área
mobile

Línea de trabajo

Start in lib/screens/sessions/session_detail_screen.dart, which this issue extends from #118, and look at how loadSession's null result and permission or moderation refusals are handled before the screen builds. The starting example is lib/screens/retry_screen.dart, which shows the Refresh and Back pattern. Done means a previously visible meeting that becomes unavailable shows only the unavailable message, passes test/screens/sessions/session_detail_screen_dp_r07_test.dart, and leaves flutter analyze clean. Wait for #118 to land before starting.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

moderation

What to build

Replace meeting details when a previously visible meeting becomes unavailable. Clear the old title, host and location so blocked or hidden content cannot remain on screen from an earlier load.

Files

Steps

  1. When loadSession returns null or a permission/hidden-content refusal, clear the stored meeting before building the screen.
  2. Show “This session is unavailable.” with Refresh and Back actions. Do not keep its old title, host or location visible.
  3. Give the same unavailable message whether the meeting is missing, blocked or hidden by moderation. Test a previously visible meeting that becomes unavailable.

Example

Previously visible test example becomes hidden → old content no longer rendered.

Check it works

In test/screens/sessions/session_detail_screen_dp_r07_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_r07_test.dart and flutter analyze.

Before starting

  • #118 — Confirm block and invalidate visibility

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

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DevDogsUGA/DogPack

Todos los issues de DevDogsUGA/DogPack

Issues similares

Más issues de Mobile Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.