Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Space library retains pages deleted in another browser tab

オープン
  • 何か問題がありますか？
#125 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

@HaningZS がすでに取り組んでいます。

2026年10月9日 から。

  • #126 @HaningZS による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
15/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
停滞
技術スタック
react, sqlite, typescript
領域
frontend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
TypeScript
スター
4.8k
フォーク
690
平均マージ
1日 15時間
マージ済み PR（30日）
43

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

CopilotKit/OpenDots のほかの issue

CopilotKit/OpenDots の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。