Improve search public API implementation
Open
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
Description
We should move a way from the use of global functions for this API implementation and do a search library such @nextcloud/search
Todo
-
nextcloud/searchrepo/project - Resolve confusion with naming
callbacksee : https://github.com/nextcloud/server/pull/43963#discussion_r1513578002 - https://github.com/nextcloud/documentation/issues/11544
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 locating the current search public API implementation and its global functions in the Nextcloud server repository, then review the proposed @nextcloud/search project. Resolve the callback naming confusion using the linked pull request discussion and consult documentation issue 11544. Done means the API implementation uses the search library and the outstanding naming and documentation questions are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100