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

Space library retains pages deleted in another browser tab

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

Los mantenedores suelen responder en 2 días

@HaningZS ya está trabajando en esto.

Desde el 9/10/2026.

  • #126 de @HaningZS — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
15/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
react, sqlite, typescript
Área
frontend

Línea de trabajo

Start with mergePageSnapshot and the page-list polling path in the Space library client, alongside SpaceLibrary, SpaceWorkspace and PageDocument, and check how they use GET /api/spaces/:spaceId/pages. Done means a fresh complete list drops a row deleted in another tab while keeping newly created pages, newer saved revisions, local tombstones, and an open unsaved draft. Open PR #126 already targets this, so coordinate with it rather than starting a parallel fix.

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

Descripción

Problem

A Space library keeps showing a page after the same owner deletes it in another browser tab. Successful later polls already omit the deleted page, but mergePageSnapshot keeps every previously known row forever unless this particular component issued the deletion itself.

This is an ordinary single-owner, two-tab workflow, not a request for multi-user collaboration or a recycle bin.

Reproduction

  1. Open the same Space in tabs A and B, with a saved page visible in both.
  2. Keep A on the page library. In B, open the page and use Page actions → Delete page.
  3. Wait for A's regular page-list polling to complete successfully more than once.
  4. A still shows the deleted page even though GET /api/spaces/:spaceId/pages omits it and the page API returns 404.

Expected: a successful fresh complete list should remove the deleted library row. If that page is open for editing in A, keep its local draft available and explain the external deletion rather than silently unmounting the editor.

Actual: the deleted row remains until the Space component is remounted/reloaded; opening or saving it produces a not-found error.

Verification

  • Upstream main at 625452e, Node.js 24.16.0, Chrome on macOS.
  • Reproduced with two actual browser pages using the real SpaceWorkspace, SpaceLibrary, PageDocument, ReactDOM StrictMode, repository CSS, and the project's real Hono page API / SQLite store with synthetic in-memory data.
  • After B deleted a parent, its child was correctly reparented on the server. A completed two further list polls, but still displayed one deleted-parent row.
  • No Intelligence/model/Slack/voice credentials or live cloud services were needed.

Fix boundaries

The existing union merge protects a newly created page from a list request that started before creation. A fix should preserve that protection, newer saved revisions, and local-deletion tombstones. It also needs to avoid older overlapping list responses resurrecting deleted rows and preserve an already-open unsaved draft.

I am preparing a bounded client fix with regression tests and browser checks. This is separate from #114's version-history/trash/import-export proposal: its polling path still uses the same union merge.

Lenguaje dominante
TypeScript
Estrellas
4.8k
Forks
690
Merge medio
1 d 15 h
PR fusionados (30 d)
43

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 CopilotKit/OpenDots

Todos los issues de CopilotKit/OpenDots

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.