I8 - Captures on the rig: list, usage, removal only on request

Open
  • Is something wrong?
#151 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend

Research direction

Start by reading parent issue #140 and the requirements for I1 and I4, since this work depends on both. Use the simulator to test listing captures, tracking preset references, refusing removal when referenced, and removing an unreferenced capture; also verify the UI reads the list back. Done means all four behaviors are tested and no removal happens automatically outside I4's whitelist eviction rule.

Written by the indexing model from the issue text.

Description

enhancement

Parent: #140. Depends on I4.

Required behaviour

  • "What captures are on my FM9?" lists each installed capture with its source record (I1) and which stored presets reference it.
  • The usage index is what I4's eviction reads; a referenced capture is never evicted.
  • Removal is only on request ("remove the Friedman capture"), refuses while a stored preset references it and names the preset, and runs read-back after.
  • Nothing is removed automatically outside I4's whitelist eviction rule.

Acceptance

  1. Test: list, reference tracking, refuse-to-remove-referenced, remove-unreferenced (sim).
  2. UI read-back of the list.
Dominant language
Python
Stars
7
Forks
3
Avg merge
2h 28m
Merged PRs (30d)
51

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 monzta1/ToneCommand

All issues in monzta1/ToneCommand

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.