Views: only way to sort in a view is to go to the Table view, no way to add a sort in the other views
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Search first
- I searched and no similar issues were found
What Happened?
Currently, the only way to add a sort to a view is to change to the Table view, and right click on the header of a column to either sort by ascending or descending order. If you add multiple sorts, you can manage them through the 2 arrows button on the top right of the view, and this button shows up independently of the type of view (like all the buttons on that section), which is good. Whats not good however is that if Im on the List or Gallery view, there is no way for me to ADD a new sorting option, I have to change to the Table view.
What is needed: on the Sort button, there should be a button like " + New sort " or something like that, and as the options it should show all the columns that show up in the Table view
Reproduce the Bug
.
Expected Behavior
We should be able to add a new Sort by being on any View, not just the Table view
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
No response
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
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
No files or tests are named. Reproduce the issue in List and Gallery views, then trace the existing Sort control and the Table-view sorting flow. Done means a new sort can be added from every view using the columns available in Table view, without switching views; add or run the relevant UI tests if the project has them.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100