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

[FEATURE] "Delete all my data" in-app control

Abierto
  • ¿Algo no está bien?
#116 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@Jberma23 ya está trabajando en esto.

Desde el 9/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement triage
Description

Per 0007 — Authentication, account recovery, and data-deletion behavior: there's no server-side data to delete (local-only architecture, 0001), but relying on "just uninstall the app" to delete data isn't discoverable or explicit enough. Build an in-app action that immediately wipes the local encrypted database.

Scope: a settings-level "Delete all my data" control and its confirmation/execution flow. Does not include any server-side deletion (none exists) and does not include the backup/export flow — this is destructive, one-way local deletion only.

Acceptance Criteria
  • Discoverable "Delete all my data" action exists in-app (e.g., in settings)
  • Action requires explicit confirmation before executing (destructive, irreversible — this audience is often tired or distracted, so no accidental one-tap deletion)
  • Confirmation copy is plain-language and states clearly that this cannot be undone
  • Executing the action wipes the local encrypted database immediately
  • After deletion, app returns to a clean/first-run state without crashing or showing stale data
  • Meets WCAG-aligned accessibility requirements (screen reader labels, no color-only affordances, adequate touch target size) for both the control and confirmation step
  • The feature/s being implemented are covered by unit tests - If not, create tests for them on this ticket
Additional Info and Resources
  • Source: 0007-authentication-recovery-deletion.md, "Data deletion" section
  • Directly satisfies the MVP exit-criteria checklist item on documented deletion behavior (referenced in the ADR)
  • Related: onboarding copy about backup responsibility is tracked as a separate ticket, since deletion is unrecoverable and users should understand backup is on them before they ever need this control
QA
  • Trigger deletion and confirm local database is actually wiped (not just hidden in UI)
  • Confirm confirmation step blocks accidental single-tap deletion
  • Test with a screen reader (VoiceOver/TalkBack) that the control and confirmation are announced clearly
  • Confirm app doesn't crash or show broken state immediately after deletion
Lenguaje dominante
TypeScript
Estrellas
9
Forks
4
Sin PR fusionados en 30 d

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 rubyforgood/alongwithyou

Todos los issues de rubyforgood/alongwithyou

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.