Per-run report: what was removed, per folder

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
desktop

Research direction

Start by tracing how a clean run reaches the finished screen and how the engine records removals in ~/Library/Logs/Wisp/. Identify where that screen can read the per-run log and present the removed folders with the space freed for each. Done when the expandable list matches the log and includes a link to it.

Written by the indexing model from the issue text.

Description

enhancement good first issue

After a clean, show exactly which folders were removed and how much each freed, with a link to the log. The engine already records every removal in ~/Library/Logs/Wisp/; the app does not surface it yet.

Done when: the finished screen has an expandable list that matches the log.

Dominant language
Swift
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from karanzykx/wisp

All issues in karanzykx/wisp

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.