nextcloud / nextcloud/collectives

Use Text API endpoint to list attachments

Open
#1,038 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: api technical debt
Dominant language
JavaScript
Stars
195
Forks
51
Avg merge
1d 2h
Merged PRs (30d)
48

Description

Once we drop support for Nextcloud 26, we should switch to use the Text API endpoint for listing attachments and drop our own getAttachments() implementation.

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 locating the current getAttachments() implementation and the Text API endpoint used for attachment listing. Confirm the Nextcloud 26 support boundary and compare the existing behavior with the endpoint; done means the custom implementation is removed and attachments are listed through the Text API.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.