Skip to content

How should m.room.canonical_alias be handled on room upgrade #2142

Open
@olivia-fl

Description

@olivia-fl

Link to problem area: https://spec.matrix.org/v1.14/client-server-api/#server-behaviour-19

Issue

Step 4 of server behavior on the room upgrade endpoint is:

Moves any local aliases to the new room.

The spec does not mention what should happen with m.room.canonical_alias explicitly. On synapse, it appears that local aliases are removed from m.room.canonical_alias on the old room, and added to m.room.canonical_alias on the new room.

Metadata

Metadata

Assignees

No one assigned

    Labels

    clarificationAn area where the expected behaviour is understood, but the spec could do with being more explicit

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions