|
|
|
@ -6,12 +6,12 @@ rooms staying the same type leading to trouble.
|
|
|
|
|
|
|
|
|
|
## Proposal
|
|
|
|
|
|
|
|
|
|
This MSC proposes that the room upgade API MUST copy the [room type](https://spec.matrix.org/v1.2/client-server-api/#types)
|
|
|
|
|
This MSC proposes that the room upgrade API MUST copy the [room type](https://spec.matrix.org/v1.2/client-server-api/#types)
|
|
|
|
|
over to the new room. Otherwise clients cannot trust that to happen and [Spaces](https://spec.matrix.org/v1.2/client-server-api/#spaces)
|
|
|
|
|
or [MSC3588](https://github.com/matrix-org/matrix-spec-proposals/pull/3588) Story rooms may incorrectly become
|
|
|
|
|
normal rooms breaking user-experience.
|
|
|
|
|
|
|
|
|
|
The Spec currently specfies this in [section 11.32.3. server behaviour](https://spec.matrix.org/v1.2/client-server-api/#server-behaviour-16):
|
|
|
|
|
The Spec currently specifies this in [section 11.32.3. server behaviour](https://spec.matrix.org/v1.2/client-server-api/#server-behaviour-16):
|
|
|
|
|
|
|
|
|
|
> 2. Creates a replacement room with a `m.room.create` event containing a `predecessor` field and the applicable `room_version`.
|
|
|
|
|
|
|
|
|
|