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

feat: Add chat thread deletion functionality

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

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

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript, typescript
領域
authentication, backend, documentation, frontend, full-stack, testing

調査の方向性

Start by reading ThreadHeader.jsx and threads.controller.ts, then locate the ThreadService, thread-list UI, API documentation, and existing service/API/UI test patterns. Implement the authorized DELETE /api/threads/{threadId} flow with confirmation and related-resource cleanup, while first resolving the soft-delete versus permanent-delete requirement. Done means the UI, endpoint, cascade cleanup, permission and error handling, tests, and documentation satisfy all listed acceptance criteria.

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

説明

Summary

Implement a feature that allows users (and admins where appropriate) to delete entire chat threads.
The deletion should remove all messages belonging to the thread from both the UI and the underlying data store while preserving data integrity for related entities.

Motivation

  • Users currently have no way to clean up obsolete or unwanted conversation histories.
  • Provides better privacy controls and reduces storage bloat.
  • Aligns with the roadmap for improving chat management capabilities.

Acceptance Criteria

  1. UI

    • A Delete Thread button appears on the thread header (visible to the thread owner and admins).
    • Clicking the button opens a confirmation modal with Cancel and Delete options.
    • After confirmation, the thread disappears from the thread list with a smooth fade‑out animation.

  2. Backend

    • API endpoint DELETE /api/threads/{threadId} that:
      • Authenticates the requester.
      • Checks that the requester is the thread owner or has admin privileges.
      • Performs a cascade delete of all messages linked to the thread.
    • Returns 204 No Content on success, with appropriate error codes otherwise (403, 404).

  3. Data Integrity

    • All foreign‑key constraints remain satisfied after deletion.
    • No orphaned attachment files or metadata remain; clean up any related resources.

  4. Testing

    • Unit tests for the service layer confirming cascade deletion.
    • Integration tests covering the API endpoint (success, unauthorized, non‑existent thread).
    • End‑to‑end UI test verifying that the button appears, modal works, and the thread is removed from the list.

  5. Documentation

    • Update the README/API docs with the new endpoint definition and usage examples.
    • Add a Chat Thread Management section to the user guide describing how to delete a thread.

Edge Cases & Considerations

  • Permissions: Ensure that only authorized users can delete threads; regular members should not see the delete
    option for threads they don’t own.
  • Undo/Recovery: Evaluate whether a soft‑delete (with a 30‑day recovery window) is needed. If not, clearly state
    the action is permanent in the confirmation modal.
  • Concurrent Deletion: Handle race conditions where two users might attempt to delete the same thread
    simultaneously (idempotent delete operation).

Implementation Approach

  1. Add a DeleteThread button in ThreadHeader.jsx (or equivalent component).

  2. Create a confirmation modal component ConfirmDeleteModal.

  3. Implement the backend handler in threads.controller.ts (or language‑specific equivalent) that invokes the service
    layer.

  4. Extend the ThreadService to perform a cascade delete of associated messages and clean up attachments.

  5. Write unit, integration, and E2E tests.

  6. Update API documentation and user guide.

主要言語
TypeScript
スター
6k
フォーク
868
平均マージ
2日 8時間
マージ済み PR（30日）
55

環境構築

はじめの一歩

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

CopilotKit/OpenDots のほかの issue

CopilotKit/OpenDots の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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