Per-run report: what was removed, per folder
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
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
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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from karanzykx/wisp
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 39/100
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Add Flutter/Dart pub cache and Conda package cache categoriesPossibly taken @karanzykx claimed this today. Openenhancement good first issue help wanted
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
enhancement help wanted safety
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:cli documentation good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 94/100
isaaclins/freesnitch#430 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day