Collections: When removing keys, return which keys are actually removed
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
I know this is difficult to implement - but it would super useful, on delete, to know which keys were removed.
This could be controlled by a flag if there are performance concerns. Maybe sometimes we're happy to risk a big performance hit in exchange for knowing what will actually happen.
One approach would be to query all keys matching a pattern before the delete, then return that list. So it sort of predicts what it'll delete. I don't know how robust this is.
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
The issue does not identify files, tests, or a specific delete entry point. First locate the collection deletion implementation and its tests, then clarify the expected behavior, performance trade-offs, and what returned keys must represent before defining completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100