nextcloud / nextcloud/spreed

Static and Dynamic capabilities: provide all configs and preferences as capabilities with 2 hashes for critical and mutable subsets

Open
#15,258 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

client: 💻 desktop enhancement feature: api 🛠️ feature: frontend 🖌️
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Current proposal:

  1. Add all the preferencies to the capabilities (e.g., PlaySound is missing)
  2. Indirectly (without the structure change) divide all the capability values into 2 subsets:
    1. With actually critical-to-change values requiring application restart to apply
      • For instance: backend version, federation.enabled, HPB-related configs
    2. With changeable configs
      • The most of the configs and conditional features
  3. Add two new hash headers for the values above
    1. Aka X-Nextcloud-Talk-Capabilities-Static-Hash (or, immutable, persistent)
    2. Aka X-Nextcloud-Talk-Capabilities-Dynamic-Hash (or mutable, fluid)
  4. The current 'X-Nextcloud-Talk-Hash header includes both types of values is kept for backward compatibility
  5. On Frontend:
    1. On top of the existing capability manager, add a reactive store adapter
    2. Provide public API:
      • Get capabilities
      • (Un)Subscribe to hashes invalidation
      • (Un)Subscribe to capability change

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

No files or tests are named. Start by locating the existing capability manager and handling for the X-Nextcloud-Talk-Hash header, then trace how capabilities are exposed to the frontend; done means the proposed static and dynamic hashes, backward-compatible header, and subscription APIs are defined across the affected layers.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.