nextcloud / nextcloud/recommendations
Request etag
Open
Nobody has claimed this yet.
1. to develop
enhancement
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 19
- Avg merge
- 6d 15h
- Merged PRs (30d)
- 9
Description
The request for ocs/v2.php/apps/recommendations/api/v1/recommendations doesn't return the etags. On the client side, we never know if the preview has changed, so we're forced to request file information (PROPFIND) to determine if anything has changed.
We're asking for the etag field to be added to the response items.
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 at the handler for ocs/v2.php/apps/recommendations/api/v1/recommendations and trace where its response items are assembled. Add the etag field to those items, then confirm the endpoint response exposes it so clients can detect preview changes without an extra PROPFIND request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100