nextcloud / nextcloud/tables

API: Add filters

Open
#2,985 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
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.

Since we have relations it can be necessary to fetch only certain rows of a table, while it isn't possible to create views for that.

Example shopping cart: Imagine you have a shopping cart connected to a user, but multiple products that can be in the shopping cart (1-n relation in my example, would also be valid for n-m). The product rows define into which shopping cart row they belong. So: When I know the shopping cart, I could fetch the specific rows belonging there.

Currently, rows cannot be filtered server side and need to be filtered by the calling application, which will be very slow for big tables.

Describe the solution you'd like

Be able to add filters to rows/views GET requests, based on normal column values but also based on creator/creation date etc.

Describe alternatives you've considered

Filtering client side, which is really slow for big tables.

Additional context

No response

Contributor guide

Open the contributing guide

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.

Research direction

No file or test is named. Start by tracing the rows and views GET API entry points and checking how existing query parameters are parsed and applied. The work is done when server-side filters support normal columns and creator or creation-date values for the relevant GET requests, with documented behavior and coverage for the filtering cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend, database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.