matrix-org / matrix-org/matrix-spec
API for deleting user & room account_data (SPEC-431)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Submitted by @matthew:matrix.org
We seem to have deliberately avoided to specify a DELETE for account_data. Unsure why (possibly to simplify the /sync responses when it disappears?), but it's not ideal that as a result empty account_data objects start to stack up where people try to delete them
(Imported from https://matrix.org/jira/browse/SPEC-431)
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 reading the existing Matrix specification for user and room account_data, then review the issue discussion and the linked SPEC-431 context. Done means the specification has an agreed DELETE operation for both account_data types, including its behavior when data disappears from sync responses.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100