Add an explicit local generation cleanup workflow
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, node.js
Research direction
Read src/server.js and src/apps.js to trace app identifier handling and preview lifecycle, then inspect ui/app.html and docs/api.md for the user flow and API conventions. Start by checking existing PRs as the issue requests. Done means a deliberate, documented delete flow is designed and implemented with temporary synthetic folder tests for active previews and missing apps.
Written by the indexing model from the issue text.
Description
Area: Artifacts
Priority: P3
Difficulty: advanced
Context
generated/ grows over time and there is no supported delete action in Mission Control.
This task is based on source inspection at e4bbac7. It does not claim a live-provider reproduction.
Scope
Design an explicit user-triggered delete operation for one generated app, including stopping its preview and clearly describing data loss. This issue authorizes design work, not automated cleanup of user artifacts.
Starting points
Acceptance criteria
- Validate the app identifier and restrict deletion to the intended generated app.
- Require a deliberate confirmation in the UI and document irreversible effects.
- Tests use temporary synthetic folders and cover active-preview cleanup and missing-app behavior.
Contributor notes
Check existing PRs before starting and comment with a short approach for larger changes. Follow CONTRIBUTING.md. Use synthetic fixtures and temporary directories, keep credentials out of commits, and run npm run verify plus git diff --check. Default validation must not spend model credits or require SigNoz.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 9h 15m
- Merged PRs (30d)
- 10
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 himanshu748/devswarm
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
himanshu748/devswarm#75 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
himanshu748/devswarm#72 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
himanshu748/devswarm#69 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
himanshu748/devswarm#61 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
himanshu748/devswarm#43 ·
Maintainers usually reply within 1 day
All issues in himanshu748/devswarm
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OWASP/CheatSheetSeries#3018 ·
Maintainers usually reply within 1 day
-
Radix number block generates NaN after switching a negative or decimal number to binary, octal or hexPossibly taken @matthewalberto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mit-cml/appinventor-sources#4246 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
GoogleChrome/modern-web-guidance-src#3675 · 2 comments ·
Maintainers usually reply within 1 day