API: endpoint to delete data based on filter
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Is your feature request related to a problem? Please describe.
when using Tables for Nextcloud internal processes, we need to clean up old data (LTD Process)
Describe the solution you'd like
Current API deletion endpoint is dependent on the rowID.
The API is called from a bash script were we do not have knowledge about the rowID.
We do have the value of one column.
- Option 1: create a deletion endpoint which allows querying with parameters (like column-id & text)
- Option 1: create a search endpoint which allows querying with and returns the rowID => which can then be used with the existing delete endpoint
Describe alternatives you've considered
No response
Additional context
No response
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 locating the existing API deletion endpoint that requires a rowID and review its surrounding API conventions. Compare the proposed filter-based deletion and search-then-delete approaches, then define the request parameters, response, and safety behavior. Done means the chosen API flow can remove the intended rows without prior rowID knowledge and is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100