Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Space library retains pages deleted in another browser tab

Aperta
  • Qualcosa non va?
#125 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@HaningZS ci sta già lavorando.

Dal 9/10/2026.

  • #126 di @HaningZS — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
15/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
react, sqlite, typescript
Ambito
frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
4.8k
Fork
690
Merge medio
1g 15h
PR unite (30g)
43

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CopilotKit/OpenDots

Tutte le issue di CopilotKit/OpenDots

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.