Keep folders displayed when running an unified-search
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
NC 23 implements this new cool feature that when you search for something in the unified-search, it will also filter the current files list.
However, if you search for something you cannot browse your folder hierarchy to find files matching your unified-search input: If the file you are looking for is not in the current folder, you have to reset the unified-search, open another subfolder you want to explore, and launch a new unified-search. This, until you find the good folder where the file you're looking for lives.
Describe the solution you'd like
When filtering the files list, it might be better to continue display folders so that the user can more easily drill-down in the folder hierarchy to find the file she's looking for.
Describe alternatives you've considered
I've developped an app to improve searching for files: https://framagit.org/StCyr/files_advancedsearch
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 tracing the unified-search filtering of the current files list in the Nextcloud server repository. The change is complete when folders remain visible during filtering and users can drill down through the folder hierarchy to find matching files without resetting the search.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- frontend, search
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100