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

mtg: unread dot on the "What's new" menu entry

Cerrado
  • ¿Algo no está bien?
#180 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #183 de @omikron-agent — fusionado

Evaluación

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

Línea de trabajo

Start with the Release notes module and the menu entry and page entry points that use it; inspect how Releases expose their notes and how the app currently stores device-local state. Add vitest coverage through the module’s public functions for the four listed cases, then verify the menu dot and page behavior match them. Done means unread notes show a dot, opening the page clears it, first visit stores the current Release silently, and storage failures do not break the app.

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

Descripción

ready-for-agent

Parent

#175

What to build

A player sees a small dot on the "What's new" menu entry when a Release brought Release notes they have not seen yet, and the dot disappears once they open the page. There is no popup, dialog or toast; the PWA's silent autoUpdate stays unchanged.

The unread logic lives in the Release notes module: given the last-seen Release (or none) and the Releases, it decides whether the dot shows and what value to store.

  • First visit (nothing stored): store the current Release silently, show no dot, so a new visitor is not nagged about history.
  • Stored Release older than a Release with notes: show the dot.
  • Stored Release older only than Releases without notes: no dot.
  • Opening the page stores the newest Release.

The last-seen Release is kept per device in localStorage, wrapped so that blocked or throwing storage degrades to "no dot". No per-Account tracking.

Acceptance criteria

  • The menu entry shows a dot exactly when the unread logic says so
  • Opening the "What's new" page clears the dot; a later Release with notes brings it back
  • A first visit shows no dot and stores the current Release
  • Blocked localStorage shows no dot and does not break the app
  • No update popup or dialog is added
  • vitest tests, through the module's public functions, cover: first visit; older stored Release with newer notes; older stored Release where the newer Releases have no notes; opening the page stores the newest Release
Lenguaje dominante
TypeScript
Estrellas
0
Forks
1
Merge medio
4 h 25 min
PR fusionados (30 d)
90

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

  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 myOmikron/code

Todos los issues de myOmikron/code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.