nextcloud / nextcloud/tables

Possibility to expand or restrict sort or filter settings in a view (with the possibility of returning to the view's default values)

Open
#1,366 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

In the settings of a view, you can apply rankings or filters.

The current problem is that it is locked. I use my experience in terms of UX from my previous job to say and explain this.

In my previous job, I built websites for tourist offices. In these websites, there are lists of information (hotels, restaurants, campsites, etc.), and even lists of activities or accommodations that can be booked (after using a search engine).

Experience has shown that people sometimes make too limited or too broad a choice and are then bothered to recalibrate their search (go through a new search, or go to another section of the site).

The solution is to allow people to modify the constraints specified in the reservation search or applied by default to the chosen list of information.

In Tables, I am regularly bothered, especially by the default sorts (from those I defined in the view settings). By default, I put in the view settings an alphabetical sort from A to Z for the "Name" field, but I also need to be able to disable this sort to sort on another column to temporarily have another view of this information, without being forced to create another view or temporarily change the view settings (which is tedious). I can of course enable a sort on a different column, but the A to Z sort of my "Name" field persists and I don't get what I want. Finally, I ended up disabling all the sorts of my views, because they are too restrictive.

How could this improvement be transposed in Tables?

I think that the sorts and filters should appear when you click on [⋅⋅⋅]: sort, operator, value. All of them should be editable. As soon as a change is made, a "reset" button should appear, so that the sorting and filtering parameters can be restored to their default values ​​defined in the view settings.

Describe the solution you'd like

Read above

Describe alternatives you've considered

None

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

The issue does not name implementation files, tests, or a code entry point. Start by locating the Tables view controls for sorting and filtering; the work is done when users can edit those parameters temporarily and reset them to the view's default values.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.