get all shares for client
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Currently android client is using webdav search to get all shares, but this is too slow.
Web UI is using those three requests:
http://localhost/nc/ocs/v1.php/apps/files_sharing/api/v1/shares?format=json&shared_with_me=true&include_tags=true
http://localhost/nc/ocs/v1.php/apps/files_sharing/api/v1/shares?format=json&shared_with_me=false&include_tags=true
http://localhost/nc/ocs/v1.php/apps/files_sharing/api/v1/remote_shares?format=json&include_tags=true
Where the latest one has a different data structure.
Would it be possible to have one endpoint for those three with the same data structure like files_sharing/api/v1/shares, as we use this already?
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 reviewing the three existing endpoints in the issue: files_sharing/api/v1/shares with both shared_with_me values, and files_sharing/api/v1/remote_shares. Compare their response structures and how the web UI consumes them. Done means a single endpoint can return all three share sources using the files_sharing/api/v1/shares data structure, including tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100