nextcloud / nextcloud/server

Show hidden files when searching

Open
#57,654 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

[!TIP]

Help move this idea forward
  • Use the 👍 reaction to show support for this feature.
  • Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
  • Subscribe to receive notifications about status changes and new comments.

Is your feature request related to a problem? Please describe.

Hi, today I've noticed whilst synchronizing through the desktop client that some python venvs were on my cloud so I tried to find and delete them from the web ui to remove them before the sync would end.
I usually start my envs with venv or .venv so I searched for the first term which didn't returned the latter, I thought of the hidden files and started typing .venv but even then no result were returned.
I then found that you had to toggle an option to show hidden files that solved my issue.

Describe the solution you'd like

I think that the client should display hidden files when the query starts with a dot. Such a query could also be to search for a file extension but I don't think this would deteriorate this use case whilst simplifying the hidden files use case.

Describe alternatives you've considered

The client could also display a tip to activate hidden files if only hidden results are found for a request.

Additional context

As I was sure that the folders were present, I quickly realized that something was wrong but I think that if you are unsure, this could lead to think that the file is absent.

When hidden files are shown :
Image

When they aren't (makes you think that there is no match at all) :
Image

Ps: AS this is a small issue I thought that it was more a feature request than a bug but I may be wrong. And thanks for this project, it is really helping !

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 source file or test is named in the issue. Start by tracing the web UI's file search and its hidden-file visibility behavior, then check how queries beginning with a dot are handled. Done means a dot-prefixed search can find hidden files without requiring the visibility toggle, with coverage for the behavior.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.