Skip to content

event examples include spurious 'age' field #1524

Closed
@richvdh

Description

@richvdh

most of the event examples include an age field, which isn't really part of the event - in particular it will be absent over federation. /sync and /messages will add an age, but put it in the unsigned object. /intialSync probably does put an age where the examples suggest, but it's deprecated.

The example for m.room.redaction puts age under unsigned, but I'm not sure that's very clear either.

Basically I think we should remove both age and unsigned from these examples.

Metadata

Metadata

Assignees

No one assigned

    Labels

    spec-bugSomething which is in the spec, but is wrong

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions