dangling resources
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
While developing lf-sync, I found that I created many resources which are now dangling in the graph with little hope of being recovered. Should those get cleaned up somehow?
Contributor guide
No contributing guide indexed for this repository
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 examining how lf-sync creates resources and how the graph represents resources that are no longer reachable. Define the expected cleanup or recovery behavior before locating the relevant resource-lifecycle entry points; done should mean the project has an agreed and implemented way to handle dangling resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100