stacklok / stacklok/toolhive-registry-server
As a registry API consumer, I want to include soft-deleted entries in query results, so that I can support incremental sync and moderation workflows
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 27
- Forks
- 15
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 16
Description
The upstream API spec added a query parameter to handle soft deleted entries. Soft delete means records are never physically removed from the database. Instead, a status field is set to deleted, which hides them from default API listings.
Details:
- Passing include_deleted=true as a query parameter reveals them again
- Since the data is preserved, deletion is reversible so setting the status back to active restores the record
- Intended for incremental sync, where downstream consumers need to learn about deletions, and for moderation/takedown workflows where metadata should remain accessible even after removal from public listings
- There is no defined retention policy.
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
No files or tests are named. Start by locating the registry API query handling and the existing filtering of records by deletion status; trace how include_deleted=true should affect listings and how the status is represented. Done means deleted entries are excluded by default, included when requested, and existing API tests cover both results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100