nextcloud / nextcloud/spreed

Deprecate unused capability

Open
#18,374 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature: api 🛠️ technical debt
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

Should be deprecated / removed from API side as well
cc @nickvergessen

Originally posted by @Antreesy in #18355

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 with the API-side capability discussed in the reference to #18355 and trace where it is defined and exposed. Confirm that it is unused, then deprecate or remove it consistently and verify that the API no longer advertises it.

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
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.