nextcloud / nextcloud/fulltextsearch
Full-text search results provided through unified search API do not provide full resource URL
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Search results through the unified search API are generally expected to provide a full url that the client applications can open. FTS unfortunately only provides a partial relative url, such as:
/index.php/apps/files/?dir=/Documents/University/Postgraduate-2/Advanced Compiler Techniques/&scrollto=230 Intermediate Rep.pdf
Example of resource URL provided by files:
https://cloud.mycloud.com/index.php/f/1048423
A workaround was easy enough to implement in the desktop client (https://github.com/nextcloud/desktop/pull/5279), but it would be nice for the clients to not have to implement custom checks for these "incomplete" URLs :)
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 how full-text search results are assembled and exposed through the unified search API, using the relative Files URL and the full resource URL in the issue as comparison cases. Check the existing search result handling and related tests, then verify that clients receive an openable full URL without needing custom checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100