matrix-org / matrix-org/matrix-spec
spec does not say that invalid `m.relates_to` properties are rejected
Open
Nobody has claimed this yet.
A-Client-Server
help wanted
spec-bug
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
If someone tries to send an event with an m.relates_to property which is not an object (for example, m.relates_to: null, per https://github.com/matrix-org/synapse/issues/5404), should the server reject the attempt with a 400 error, or should the m.relates_to be ignored?
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 question about invalid m.relates_to values and the linked Synapse issue. Resolve whether a non-object value should produce a 400 error or be ignored, then update the relevant Matrix specification text so the required behavior is explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100