matrix-org / matrix-org/matrix-spec
CiphertextInfo properties should be marked as required.
Open
Nobody has claimed this yet.
A-Client-Server
A-E2EE
clarification
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
https://github.com/matrix-org/matrix-doc/blob/master/event-schemas/schema/m.room.encrypted#L27-L35
Shouldn't `body` and `type` be marked as required? How should clients handle absent fields?
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
Open event-schemas/schema/m.room.encrypted in the matrix-doc repository and inspect lines 27-35, focusing on the CiphertextInfo properties body and type. Compare their schema declarations with nearby required properties and determine the expected handling of absent fields. Done means the schema and its guidance consistently identify whether body and type are required.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100