nextcloud / nextcloud/server

[Enh] : Let's add a `searchFrom` for search providers.

Open
#50,587 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Some search filters/providers need to search from multiple places for example as in https://github.com/nextcloud/server/pull/50550 dav app search provider needs to search from events, contacts ...

  • searchFrom should probably be an array (a list of all places/providers to search)
  • The ID should be used uniquely to identify the provider and not specify where to search from

Also using the app id is not a good choice as one app can have multiple providers registered (e.g. dav has Contacts, Events and Tasks search)

cc: @Altahrim

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

Start by reviewing PR #50550 and the existing search-provider registration and filtering flow in the Nextcloud server. Identify how DAV exposes Contacts, Events, and Tasks providers, then define the provider identity and multi-source behavior described in the issue. Done means the API clearly supports multiple search places and uniquely identifies each provider.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend-api-design, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.