nextcloud / nextcloud/server

Fuzzy Files filename search

Open
#36,619 0 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: files feature: search
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.

Note: I have searched the issues for a similar one but haven't found any. So I would first like to apologise if this issue already exist. I would also like to apologise if this behaviour is only related to my setup.

Is your feature request related to a problem? Please describe.
When I type a query that is not the exact title of the file or the folder I am looking for, no results are found.

Example:

  1. I search for "fracture coude" and get these results:

image

  1. I search for "fracture du coude" and get these results:

image

Describe the solution you'd like
Search for files and folders titles should maybe be fuzzy ? Depending on if I add a french article (like "du", which is "of" in english), I get very different results, and often not the ones I am looking for.

Describe alternatives you've considered

  • Typing in a blind manner all the combinations of articles around my keywords, to try to get all the results
  • Search my synchronised files using the search engine of my laptop's OS which appears to be more tolerant

Additional context
It seems that fuzzy search is usually the default on most of modern OS search boxes, I would love to have this when I search for folders or files inside Nextcloud.

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 names no files, tests, or entry points. Start by locating the existing filename and folder search implementation and its tests, then determine how fuzzy matching should behave for the shown queries; done means relevant files and folders return expected results without breaking existing search behavior.

Written by the indexing model from the issue text.

Assessment

Domain
search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.