ngless-toolkit / ngless-toolkit/ngless
Implement API to cleanup unnecessary files
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 152
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Currently if a user keeps updating their ngless version they will accumulate binaries and resources in ~/.local/share/ngless for different versions.
This can be perceived as wasteful and requires that users understand this folder structure in order to know what can and cannot be removed.
Similarly to https://github.com/ngless-toolkit/ngless/issues/15 there could be an API (--cleanup) to delete old or unused resources given the ngless version in-use.
Contributor 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.
Research direction
Start by reading issue 15 and tracing the --cleanup entry point, then inspect the versioned resources under ~/.local/share/ngless. Done means the API removes old or unused resources while preserving resources needed by the ngless version in use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100