Add an explicit local generation cleanup workflow

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

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

enhancement help wanted

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

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 himanshu748/devswarm

All issues in himanshu748/devswarm

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.