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

Delete attached photos when a feature is deleted

オープン
#4,727 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

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

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
65/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
cpp
領域
mobile

調査の方向性

No files or tests are named. Start by tracing feature deletion, discard handling, and composition versus association child handling, then verify each acceptance criterion, including nested children, orphaned photos, and the discard confirmation text.

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

説明

Current situation

When a feature is deleted, its attached photos stay on the device and in the project. This leaves unused files behind, and with the composition relation supported (https://github.com/MerginMaps/mobile/issues/2315) more features will be deleted automatically, so more orphaned photos could pile up.

Proposed solution

When a feature is deleted, delete its attached photos as well. This also applies to child features deleted through a composition relation (for example, if a parent feature is deleted, then its children should be deleted as well)

Acceptance criteria
  • Deleting a feature deletes its attached photo(s)
  • Deleting a parent with composition children deletes the photo(s) of all deleted child features (including nested ones)
  • If child features are created while adding a parent, and the parent is discarded without saving, the photos of those child features are deleted too
  • Deleting a parent with association children does not delete the children's photos (and neither the children, check acceptance criteria of (https://github.com/MerginMaps/mobile/issues/2315)
  • when discarding a parent feature with composition children, the delete confirmation text mentioned that the attached photos will also be deleted

Related to: https://github.com/MerginMaps/mobile/issues/2315

主要言語
C++
スター
389
フォーク
88
平均マージ
3日 1時間
マージ済み PR(30日)
22

環境構築

はじめの一歩

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

MerginMaps/mobile のほかの issue

MerginMaps/mobile の issue をすべて見る

似ている issue

C++ の issue をもっと見る

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

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