matrix-org / matrix-org/matrix-widget-api
Capabilities re-negotiation doesn't really work
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 95
- Forks
- 24
- Avg merge
- 16h 16m
- Merged PRs (30d)
- 1
Description
The API surface we expose doesn't support iterative changes to capabilities very nicely, so we should change that.
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 public TypeScript API surface for capability negotiation. Determine how iterative capability changes are currently represented and what behavior the API should support; done means capabilities can be renegotiated repeatedly through the exposed API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100